What I’m trying to do:
Host a .index and reverse proxy a Jellyfin container
My domain is inaccessible and returns Cloudflare’s 522 errors when I try to load it up. I figure if I manage to access my .index, the reverse proxy will also work. I have had all this working before, but I have seemingly broken in when I did a fresh install of OpenMediaVault.
My setup:
OS: OpenMediaVault 4 running on a ThinkServer TS130, containers are run in a Docker environment.
Steps I have taken
1. Changed DNS servers in OpenMediaVault and my Asus-Merlin router to 1.1.1.1 and 8.8.8.8
2. Disabled firewall in Asus-Merlin router
2.1 Forwarded ports 443 and 80 in Asus-Merlin router and on OMV machine.
3. Created an .index with resources at /path/www/goph
4. Setup my domain with Cloudflare
curl ifconfig.me
returns the same IP as in the top-level record
4.1 Configured SSL, Caching and Page Rules following GitHub - PGBlitz/PGBlitz.com: Welcome to https://PGBlitz.com ~ Rapidly deploy multiple-hasty Docker Containers through Ansible with local or Unlimited Google HD Space! VISIT NEW SITE >>> https://github.com/PlexGuide/PlexGuide.com
5. Setup a Cloudflare DDNS container (joshuaavalon/cloudflare-ddns) to update my IP to the Cloudflare records.
docker run
-d
–restart unless-stopped
–name=cloudflare-ddns
-e ZONE=goph.no
-e HOST=goph.no
-e EMAIL=censored@gmail.com
-e API=censored
-e TTL=1
-e PROXY=true
joshuaavalon/cloudflare-ddns
6. Setup a Caddy container (abiosoft/caddy)
docker run
-d
–restart unless-stopped
–name=caddy
–cap-add=NET_ADMIN
-e CLOUDFLARE_EMAIL=censored@gmail.com
-e CLOUDFLARE_API_KEY=censored
-e PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-e ACME_AGREE=true
-v /sharedfolders/appdata/caddy/.caddy:/root/.caddy:rw
-v /sharedfolders/appdata/caddy/Caddyfile:/etc/Caddyfile:rw
-v /srv:/srv:rw \ #(this is the path to my .index)
-p 2015:2015/tcp
-p 443:443/tcp
-p 80:80/tcp
abiosoft/caddy
6.1 Configuring a Caddyfile
goph.no {
root /srv/dev-disk-by-label-fsd/www/goph
tls {
dns cloudflare
}
}
6.2 Running the Caddy container, logs returned are (logs edited - removed links according to new user link limitation on the forum)
Activating privacy features… 2019/09/23 10:29:17 [INFO][cache:0xc0001ac320] Started certificate maintenance routine
Your sites will be served over HTTPS automatically using Let’s Encrypt.
By continuing, you agree to the Let’s Encrypt Subscriber Agreement at:
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
Please enter your email address to signify agreement and to be notified
in case of issues. You can leave it blank, but we don’t recommend it.
Email address: 2019/09/23 10:29:19 [INFO][goph.no] Obtain certificate
2019/09/23 10:29:19 [INFO] [goph.no] acme: Obtaining bundled SAN certificate
2019/09/23 10:29:21 [INFO] [goph.no] AuthURL: https (://) acme-v02.api.letsencrypt (dot) org/acme/authz-v3/468092978
2019/09/23 10:29:21 [INFO] [goph.no] acme: Could not find solver for: tls-alpn-01
2019/09/23 10:29:21 [INFO] [goph.no] acme: Could not find solver for: http-01
2019/09/23 10:29:21 [INFO] [goph.no] acme: use dns-01 solver
2019/09/23 10:29:21 [INFO] [goph.no] acme: Preparing to solve DNS-01
2019/09/23 10:29:21 [INFO] cloudflare: new record for goph.no, ID bea735a37dad2a1b17e8c2f38573ad65
2019/09/23 10:29:21 [INFO] [goph.no] acme: Trying to solve DNS-01
2019/09/23 10:29:21 [INFO] [goph.no] acme: Checking DNS record propagation using [192.168.1.1:53 1.1.1.1:53 8.8.8.8:53]
2019/09/23 10:29:21 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]
2019/09/23 10:29:21 [INFO] [goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:24 [INFO] [goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:26 [INFO] [goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:29 [INFO] [goph.no] The server validated our request
2019/09/23 10:29:29 [INFO] [goph.no] acme: Cleaning DNS-01 challenge
2019/09/23 10:29:30 [INFO] [goph.no] acme: Validations succeeded; requesting certificates
2019/09/23 10:29:32 [INFO] [goph.no] Server responded with a certificate.
2019/09/23 10:29:32 [INFO][jf.goph.no] Obtain certificate
2019/09/23 10:29:32 [INFO] [jf.goph.no] acme: Obtaining bundled SAN certificate
2019/09/23 10:29:35 [INFO] [jf.goph.no] AuthURL: https (://) acme-v02.api.letsencrypt (dot) org/acme/authz-v3/468095025
2019/09/23 10:29:35 [INFO] [jf.goph.no] acme: Could not find solver for: tls-alpn-01
2019/09/23 10:29:35 [INFO] [jf.goph.no] acme: Could not find solver for: http-01
2019/09/23 10:29:35 [INFO] [jf.goph.no] acme: use dns-01 solver
2019/09/23 10:29:35 [INFO] [jf.goph.no] acme: Preparing to solve DNS-01
2019/09/23 10:29:36 [INFO] cloudflare: new record for jf.goph.no, ID 2af648ebaee4c84bc6c02c9a185a8754
2019/09/23 10:29:36 [INFO] [jf.goph.no] acme: Trying to solve DNS-01
2019/09/23 10:29:36 [INFO] [jf.goph.no] acme: Checking DNS record propagation using [192.168.1.1:53 1.1.1.1:53 8.8.8.8:53]
2019/09/23 10:29:36 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]
2019/09/23 10:29:36 [INFO] [jf.goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:38 [INFO] [jf.goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:40 [INFO] [jf.goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:42 [INFO] [jf.goph.no] acme: Waiting for DNS record propagation.
2019/09/23 10:29:47 [INFO] [jf.goph.no] The server validated our request
2019/09/23 10:29:47 [INFO] [jf.goph.no] acme: Cleaning DNS-01 challenge
2019/09/23 10:29:47 [INFO] [jf.goph.no] acme: Validations succeeded; requesting certificates
2019/09/23 10:29:51 [INFO] [jf.goph.no] Server responded with a certificate.
done.Serving HTTPS on port 443
https (://) goph (dot) no
https (://) jf.goph (dot) no2019/09/23 10:29:51 [INFO] Serving https://goph (dot) no
2019/09/23 10:29:51 [INFO] Serving https://jf (dot) goph (dot) noServing HTTP on port 80
http (://) goph (dot) no
http (://) jf.goph (dot) no2019/09/23 10:29:51 [INFO] Serving http://goph.no
2019/09/23 10:29:51 [INFO] Serving http://jf.goph.no
2019/09/23 10:29:52 [INFO] Sending telemetry: success
7. Trying to access domain in a browser (tested both inside and outside network)
Returns
Error 522 Ray ID: 51ac11743e28769a • 2019-09-23 11:10:15 UTC
Connection timed out
