Skip to content

Connection issue with NPM and guacamole from some computers #4541

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pinpoint90 opened this issue May 16, 2025 · 1 comment
Open

Connection issue with NPM and guacamole from some computers #4541

pinpoint90 opened this issue May 16, 2025 · 1 comment

Comments

@pinpoint90
Copy link

pinpoint90 commented May 16, 2025

Ive setup guacamole as a proxy on NPM with ssl. It works on most private remote connections (i.e. my friends or parents house, or through cellular network), however I cant access when I use a remote computer connected to a corporate pc that is behind its own proxy.

When trying to access my guacamole server on my own domain, instead of login screen I get this error page:
"An error has occurred and this action cannot be completed. If the problem persists, please notify your system administrator or check your system logs."
It is worth to mention that rarely, once a day, I manage to get to the login screen after hours of randomly refreshing the page.

I can`t figure if the problem is in NPM or guacamole, but I suspect the problem to be a proxy/routing issue. Ive tried turning on/off all ssl settings http/2, HSTS, as well as common exploits and websockets.
Anyone know what might be the problem?

@pinpoint90
Copy link
Author

pinpoint90 commented May 22, 2025

I notice that there seem to be a 24 hour timeout where I am not able to access guacamole. When refreshing the webpage or disconnecting from guacamole, it takes 24 hours before I can connect to it again.
Maybe it is a NPM cache issue, I dont know. I am running NPM as a lxc container on a separate computer with proxmox.
I did not have this problem when running guacamole on docker on Synology NAS and using the internal reverse proxy on the nas. I belive synology uses nginx? Therefore I suspect that the problem is my NPM configuration...
Worth to mention that I also run my own domain through cloudflare (tested both with DNS proxy on and off).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant