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
Go to the Containers section in the application.
Check the exposed ports column.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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_HOSTvariable 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
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