Getting no ip about amp-dockerized

[MitchTalmadge]

Hey there! If you are referring to the line:

Webserver started on 0.0.0.0:8081

This is normal and expected. It just means that AMP is listening on all interfaces, or in other words, you can access the web panel from other computers as long as the port is not blocked by your computer or router.

Here's a good explanation from Wikipedia:

In the context of servers, 0.0.0.0 can mean "all IPv4 addresses on the local machine". If a host has two IP addresses, 192.168.1.1 and 10.1.2.1, and a server running on the host is configured to listen on 0.0.0.0, it will be reachable at both of those IP addresses.

[MajorLOL]

I cant seem to connect to the interface, i tought this was related. everything seems fine in the log tho....
Changing port gives the same result

[TABLE272]

Theres quite a few potential variables at that point. Keep in mind that running through Docker we lose amp's automatic firewall management so you'll need to port forward on both the docker container and the host OS if youre running a firewall on the host. If the port isnt open on the host, AMP in the container wont know that as it only sees its container.

Need a bit more background though, you mention doing an upgrade, have you previously been using the image with success or do you mean upgrade in the sense of moving over to this image?

[MajorLOL]

added the port in portsettings, Container port 8558 and localport fixed it,
this was not told in the setting up the container. maybe it is docker basic but not everyone knows that ;)

[MitchTalmadge]

Glad you got it worked out! I don't know what port 8558 connects to on your system, as I have not seen it used in relation to AMP.