Hey guys, I’m having an issue trying to get boringproxy started.
I have a vps that is double NAT’d.
the systems IP is 10.0.0.4 and it’s external ip is 20.x.x.241.
I have used updog to confirm that port 80 and 443 work and can connect.
when I try and start boring proxy I get…
solving challenges: example.com: no solvers available fo r remaining challenges (configured=[http-01 tls-alpn-01] offered=[http-01 dns-01 tls-alpn-01] remaining=[dns-01])
I used example.com instead of my actual domain for privacy.
is there a way to specify an external ip? or does anyone have an idea on how to resolve this?
Hi @daif, are there any other warnings reported? boringproxy will automatically check that you’re using ports 80/443 and that they are publicly accessible through the (also auto-detected) public IP.
thanks for the reply. I don’t think there is any - here’s a snip. privacy be damned! lol.
phobos:/opt/apps/boringproxy$ ./boringproxy-linux-x86_64 server -admin-domain tavecloud.cyou
2023/10/03 15:13:23 Starting up
2023/10/03 15:13:27 tavecloud.cyou: obtaining certificate: [tavecloud.cyou] Obtain: [tavecloud.cyou] solving challenges: tavecloud.cyou: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[http-01 dns-01 tls-alpn-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/1335239606/212578283706) (ca=https://acme-v02.api.letsencrypt.org/directory)’
looks ok to me, but I’m not sure.
thanks for the help
If I run
dig tavecloud.cyou I’m not seeing any DNS records for that domain. Did you set up A and/or AAAA records?
Thanks for the reply anders. I didn’t, I just pointed the root domain to my vps ip. I created another a record dns.tavecloud.cyou (pointing to my external VPS IP) and I’m still getting the same thing.
./boringproxy-linux-x86_64 server -adm in-domain dns.tavecloud.cyou
2023/10/11 14:58:02 Starting up
2023/10/11 14:58:06 dns.tavecloud.cyou: obtaining certificate: [dns.tavecloud.cy ou] Obtain: [dns.tavecloud.cyou] solving challenges: dns.tavecloud.cyou: no solv ers available for remaining challenges
The issue must have something to do with cloudflare. I used duckdns and pointed it right to the ip and it worked fine.