Skip to content
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

How to specify Custom locations correctly #3722

Open
mxm199 opened this issue Apr 25, 2024 · 7 comments
Open

How to specify Custom locations correctly #3722

mxm199 opened this issue Apr 25, 2024 · 7 comments

Comments

@mxm199
Copy link

mxm199 commented Apr 25, 2024

Good day to all!
Version 2.11.1 is installed
Guacamole is installed and is available at gua.mysite.com/guacamole . How to correctly specify the user location so that the site is immediately accessible at gua.mysite.com ?
I've tried all the options, but none of them work, even from the official guacamole help page.
image
image
or
image
not work

I will be grateful for your help!

@s0mm3rb
Copy link

s0mm3rb commented Apr 25, 2024

I'll quickly hijack your post, because I'm currently investigating an issue with custom locations, that could be related to yours
I think there might be a general problem with custom locations (I'm on 2.11.1)
as soon as I specify a custom location the host goes offline
the host file gets deleted and cannot be recreated
it throws an error that the file could not be deleted (but it was deleted)

Could not delete file: {
  "errno": -2,
  "code": "ENOENT",
  "syscall": "unlink",
  "path": "/data/nginx/proxy_host/41.conf"
}

the host works without specifying the custom location in the GUI
then add the custom location with CLI directly to the host file and reload nginx

@mxm199
Copy link
Author

mxm199 commented Apr 25, 2024

I didn't fully understand what needed to be done... I also tried to add a construction to the host file itself (from the guacamole manual)

location /guacamole/ {
    proxy_pass http://HOSTNAME:8080;
    proxy_buffering off;
    proxy_http_version 1.1;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    access_log off;
}

image

But then the container does not restart and throws a bunch of errors on this configuration. Maybe I'm closing the brackets '}' incorrectly

image

If you remove the '}' after access_log off; then there are no errors, but it still does not work

@s0mm3rb
Copy link

s0mm3rb commented Apr 25, 2024

it looks like you've added it to the nginx config not the host config
you need to add your location to the host config file located under /data/nginx/proxy_host/<some number>.conf
add your host through the GUI and watch the log which host it is
(or search the config files with grep -n "yourhost" /data/nginx/proxy_host/*)
and reload nginx /usr/sbin/nginx -s reload

or downgrade nginx to a previous version
the GUI issue with custom locations might relate to #3647 and to #3678

@mxm199
Copy link
Author

mxm199 commented Apr 26, 2024

I installed version v2.10.4 and everything worked

@JiangJuHong
Copy link

v2.11.1 The same problem exists

@irrwitzer42
Copy link

Try 2.11.2, for me that one did the trick!

@duduws
Copy link

duduws commented Jul 23, 2024

you already solved the issue? im still trying to figure out, using npm v2.11.3 and guacamole v1.5.4, can access via http without certificate in port 8080, but cant access using the proxy port with SSL. 😭

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

5 participants