Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow custom address for the gateway

See original GitHub issue

Describe the bug The gateway is set to http://0.0.0.0:8080/ while I’m connecting from an external computer through a VPN

This bug affects the app since content in not watchable directly in the WebUI

To Reproduce Steps to reproduce the behavior:

Set your API address and gateway address to 0.0.0.0 (ip4) or :: (ip6) (1.1 Set your CORS allow-origin to “*”)
Connect to the WebUI with an external computer
See that the gateway is the one from the config instead of the real (external) address

Expected behavior We should be able to set a custom gateway address

Issue Analytics

State:
Created 3 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

1reaction

tgiescommented, Aug 17, 2020

We also need this capability. The go-ipfs Docker container, as distributed, manifests this issue. Not everyone is accessing an IPFS node running locally.

0reactions

BunkerMeloncommented, Aug 24, 2020

Thank you as well @lidel

Having it fall back to ipfs.io whenever it cannot reach the “local” IPFS node gateway on the network will work great for the time being.

Looking forward to testing these new implementations