Published ports service links do not launch.

[Daemach]

Is your feature request related to a problem? Please describe.
When an endpoint is added to Portainer manually, the endpoint URL is added as the public IP so that the published ports work. If the endpoint is paired automatically with Portainer (such as through a stack file like our recommened agent stack, or via bind-mounting the docker socket) then there is no public IP entered and published ports don't work (you get a link in the form http://:port)

Describe the solution you'd like
The ideal solution would be for Portainer to auto-fill the public IP with a url the containers or services would be reachable at (such as the ip of a node in a swarm cluster).

Describe alternatives you've considered

• If there is no public IP defined, clicking on a published port link could take you to the endpoint detail page with an additional message that tells you why you're here. The explanation in the below comment could be used.
• Might be good to "tag" published ports as http or https (or nothing) ports so you can launch with the correct URL.

Additional context:
These links look like they should launch the service in a new window, but they don't do anything.
https://www.screencast.com/t/6zupzcuEc9U

[ghost]

Hi there
I think the issue is there is no public IP defined in your endpoint, if you inspect the link for the published port on your blog_wordpress service you should see it says http://:8090

To fix this;

1. Go to endpoints view
2. Click on your endpoint to see it's details
3. Add the IP of one of the nodes from your cluster
   

Now clicking on the published port in the services view should redirect you to ip_of_node_from_cluster:8090 which should resolve

Let me know if this solves your issue

[Daemach]

You're right. That fixed it. A couple of suggestions then:

• If that IP address is null, clicking on those links should take you to this endpoint page with an additional message that tells you why you're here. Your explanation above should be all they need.
• Might be good to "tag" published ports as http or https (or nothing) ports so you can launch with the correct URL.