[GH-ISSUE #71] Application listeners not bound to IPV6 #49

New issue

Closed

opened 2026-03-02 15:47:31 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 15:47:31 +03:00

Owner

Originally created by @FireAmpersand on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/71

Originally assigned to: @mkellermann97 on GitHub.

Was interested in trying out this project since I am not super fond of the PVE/PDM web interfaces but I am unable to access the WebUI on my PegaProx install via IPV6. Checking netstat, there is nothing listening on ports 5000,50015002 on IPV6 ([::]:5000, [::]:5001, [::]:5002 are missing). Only 0.0.0.0:5000, 0.0.0.0:5001, and 0.0.0.0:5002 are listening. This is an issue since I don't run dual stack in my lab. And I am sure there is some installs out there that do use IPV6 exclusively or preferred over ipv4.

I am more of a network/server admin then a developer so not sure how difficult this is to implement. I installed a Debian 13 VM and ran the deploy script from the main website (https://pegaprox.com/#download) so I haven't done anything fancy to get this running. I feel like listening on IPV6 should be a default behaviour on a quick start deploy script.

Originally created by @FireAmpersand on GitHub (Feb 22, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/71 Originally assigned to: @mkellermann97 on GitHub. Was interested in trying out this project since I am not super fond of the PVE/PDM web interfaces but I am unable to access the WebUI on my PegaProx install via IPV6. Checking netstat, there is nothing listening on ports 5000,50015002 on IPV6 ([::]:5000, [::]:5001, [::]:5002 are missing). Only 0.0.0.0:5000, 0.0.0.0:5001, and 0.0.0.0:5002 are listening. This is an issue since I don't run dual stack in my lab. And I am sure there is some installs out there that do use IPV6 exclusively or preferred over ipv4. I am more of a network/server admin then a developer so not sure how difficult this is to implement. I installed a Debian 13 VM and ran the deploy script from the main website (https://pegaprox.com/#download) so I haven't done anything fancy to get this running. I feel like listening on IPV6 should be a default behaviour on a quick start deploy script.

kerem

2026-03-02 15:47:31 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 15:47:33 +03:00

Author

Owner

@jwgn commented on GitHub (Feb 22, 2026):

Also noticed that after install. How can we configure the WebUI listener for IPv6?

@jwgn commented on GitHub (Feb 22, 2026): Also noticed that after install. How can we configure the WebUI listener for IPv6?

kerem commented

2026-03-02 15:47:33 +03:00

Author

Owner

@abyss1 commented on GitHub (Feb 23, 2026):

1 more for IPv6 Support either single stack or dual stack :)

@abyss1 commented on GitHub (Feb 23, 2026): 1 more for IPv6 Support either single stack or dual stack :)

kerem referenced this issue

2026-03-02 15:47:54 +03:00

[PR #63] [MERGED] fix(search): navigate to resources tab when jumping to a VM from search #101