You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
I
ve 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 can
t 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?
The text was updated successfully, but these errors were encountered: