Exposed port URL in the containers view is incorrect #1392

Open
opened 2026-03-22 17:25:03 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @piposeimandi on GitHub (Sep 18, 2025).

Problem Description

Currently, the URL displayed for exposed ports in the containers view is not correct. The URL points to the container's internal address instead of the correct externally exposed service URL. This causes confusion and makes it difficult to directly access the services from the interface.

Note:
The KOMODO_HOST variable has been configured correctly in the environment, so the issue is not related to a misconfiguration of this environment variable, but rather with the logic used to generate the URL.

Requirement

Fix the URL generation logic so that it correctly points to the externally accessible address and exposed port, not the internal container address.

Steps to Reproduce

  1. Go to the Containers section in the application.
  2. Check the exposed ports column.
  3. Try to access the service using the generated URL.

Expected Result

The URL should point to the public IP or domain and the exposed port, allowing direct access to the service from the UI.


Reported by: @piposeimandi

Originally created by @piposeimandi on GitHub (Sep 18, 2025). ### Problem Description Currently, the URL displayed for exposed ports in the containers view is not correct. The URL points to the container's internal address instead of the correct externally exposed service URL. This causes confusion and makes it difficult to directly access the services from the interface. **Note:** The `KOMODO_HOST` variable has been configured correctly in the environment, so the issue is not related to a misconfiguration of this environment variable, but rather with the logic used to generate the URL. ### Requirement Fix the URL generation logic so that it correctly points to the externally accessible address and exposed port, not the internal container address. ### Steps to Reproduce 1. Go to the Containers section in the application. 2. Check the exposed ports column. 3. Try to access the service using the generated URL. ### Expected Result The URL should point to the public IP or domain and the exposed port, allowing direct access to the service from the UI. --- **Reported by:** @piposeimandi
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#1392