Closed hulkhaugen closed 10 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
That's more of a question for whoever is maintaining the HA addon. We don't publish that addon and they put their own spin on it.
Our image uses ports 80 and 3000 for the user and admin guis, and 4001 for ipfs peering
Reopening, I see that the 5001 port number is listed in our container's log as well, so it needs a deeper look
It seems to be a port for go-ipfs webui, which is not relevant here. The log entry comes from the go-ipfs daemon.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
According to the documentation, and it also works, the port number is 80 and 3000, but in the log i see the following:
WebUI: http://127.0.0.1:5001/webui Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/8080
Expected Behavior
What's in the log should correspond with what is actually configured
Steps To Reproduce
Run latest version, compare log and config.
Environment
CPU architecture
x86-64
Docker creation
Container logs