Issues with Caddy to Proxy Guacamole

Help
1

Hi all,
I’ve successfully set-up a Guacamole server and have added it to my Caddyfile to reverse proxy it to the outside. However, ever since I added it to the file Caddy Server keeps crashing.
Here is my Caddyfile:

skywave.com
{
root /var/www/html
}

fdeluge.skywave.com {
proxy / 192.168.1.16:8112 {
transparent
websocket
}
tls example@domain.com
}

rwave.skywave.com {
proxy / 192.168.1.17:8112 {
transparent
websocket
}
tls example@domain.com
}

test.skywave.com {
gzip
proxy / 10.11.1.6:8080/guacamole {
transparent
}
tls example@domain.com
}

Anyone have any clues as to why it happens?

EDIT: Here are my logs from systemd

Oct 30 07:03:09 CadServ systemd[1]: Started Caddy HTTP/2 web server.
Oct 30 07:03:09 CadServ caddy[398]: Activating privacy features…2017/10/30 07:03:09 get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”: Get https://acm
Oct 30 07:03:09 CadServ systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
Oct 30 07:03:09 CadServ systemd[1]: caddy.service: Unit entered failed state.
Oct 30 07:03:09 CadServ systemd[1]: caddy.service: Failed with result ‘exit-code’.

2 
Oct 30 07:03:09 CadServ caddy[398]: Activating privacy features…2017/10/30 07:03:09 get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”: Get https://acm

Looks like it failed because it couldn’t contact the ACME server. Doesn’t seem like a Guacamole-specific error. Does your Caddy host have internet access?

3

Yes it does, if I take out the entire guacamole entry, Caddy works

4

That might be because your host can’t access the ACME server right now, but you already have certificates for the other sites in your Caddyfile, so it doesn’t need to get them.

Try curl https://acme-v01.api.letsencrypt.org/directory from the Caddy host and see what you get.

5

root@CadServ:/usr/local/bin# curl https://acme-v01.api.letsencrypt.org/directory

curl: (6) Could not resolve host: acme-v01.api.letsencrypt.org

That’s very weird. it should be able to reach the acme server. Let me check my rules

6

Yep, your server can’t reach the ACME server. Mine can, so the problem is most likely at your end, not at LetsEncrypt.

If it’s able to access other hosts, it might just be a general internet routing issue, such as a bad router between you and LE. If that’s the case, it’ll be over in a few hours, most likely.

Otherwise investigate firewall rules etc.

7

Yup! Turned out to be an issue with the firewall. Now it can reach the acme server

EDIT: Yup!! my Guacamole server can be reached now. Thanks for your help!

1 Like
9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.