mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-21 09:21:15 -05:00
[GH-ISSUE #325] Webtop/firefox in docker does not work #1389
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#1389
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @1kazekage on GitHub (Mar 11, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/325
Hi Team,
I have setup webtop or firefox in container with port 3000 targeted. Giving Bad Gateway in reaching it.
@miloschwartz commented on GitHub (Mar 11, 2025):
A gateway error usually indicates there is an issue addressing the downstream service using the target and port you entered. Can you let me know what you used?
Is Newt running in a docker container? If so, localhost will address the container itself, not the system the container is running on. If it's on the same docker network as the other services, you can use the docker container name. Otherwise, use the host LAN IP.
Can you check for any errors in the logs on Newt or the server and post them here as well please?
@1kazekage commented on GitHub (Mar 12, 2025):
As far as I remember, newt is not running on any docker network, used default config while installation. But, it is running in container.
Also, using this container below:
https://docs.linuxserver.io/images/docker-webtop/
It is like a Linux running in a container with kasmvnc for access.
And this webtop is also not running on any docker network.
Just tried for portainer via localhost ip and port and it is giving "no available server as well".
Do you recommend to run the containers including newt on same docker network and then use container name only in target?
I will check logs once back from office.
@miloschwartz commented on GitHub (Mar 12, 2025):
A docker network can be useful/simply things depending on your setup. Alternatively you can try to address the host directly using its network address rather than localhost. Make sure that what ever target you enter into Newt, you can also access via your browser locally.
@1kazekage commented on GitHub (Mar 12, 2025):
Hi, thank you for response. Everything works now. Check the target ip to see if its right, and in portainer, attached newt and my services to same network ( on which portainer is) and then rebooted the container. However, I can see now that 2 containers for newt are running, one is on default network it originally was and one on the network same as portainer and my services. Don't know what that is but everything works for me. And I do have a special case scenario which I wanted to get enabled on for past 2 months and pangolin just did it for me so effortlessly.
Amazing! Way to go!