When i try to get server i have this warning:
Hey @johantri, generally speaking you’ll want to run boringproxy on a computer that has a public IP address. If you’re running this from home, that typically means you need to set up port forwarding from your router. If you’re behind a CGNAT, or your ISP blocks ports 80/443, then port forwarding won’t work and you’ll probably need to set up a VPN or tunneling. This sort of situation is actually what boringproxy is designed for, except typically you would run it on a cloud VPS such as DigitalOcean and tunnel to other services running inside your private network.
If you’re not familiar with most of these terms, you’ll probably have a lot to learn to get up and running. But there’s nothing wrong with that if you’re interested in figuring it out! Happy to help you get started.
If you don’t want to dive in the deep end just yet, I’d recommend giving Cloudflare Tunnel a try. It’s similar to boringproxy, but Cloudflare manages most of the complexity for you.
I’m hoping TakingNames.io will eventually be a good alternative, but it’s not there yet. Also it won’t be free like Cloudflare Tunnel, though it will be end-to-end encrypted if that’s important to you.
I’m also having the same issue, while trying to setup the server on an Oracle Cloud VPS.
Despite being able to run a python http server via the same public IP address (and also via port 80) of my VPS instance.
FYI I’m using boringproxy “0.9.1 Beta”.
My Oracle Cloud Instance is using “Oracle-Linux-8.5-2022.01.24-0” image, “VM Standard.E2.1.Micro” shape.
Any help appreciated
Hey @XxniperX, thanks for the report. Do you happen to know whether it’s using IPv6 or not? Sometimes you need to open IPv6 ports separately from IPv4. At least that’s the way my ISP (Google Fiber) does it.
Thanks @anders for the reply.
I don’t have IPv6 enabled.
Will give it a try.
Actually leaving IPv6 disabled would probably be easier to debug. I was thinking if it’s enabled that could cause problems.
Can you try running Caddy on the VM and see if its auto-HTTPS work correctly?
Thanks for the reply @anders,
I’ll give Caddy a try, but probably after a break.
Will update you once I’m done.
Using a working cPanel with many web sites for many years. It fails.
[dougk@server ~]$ ./boringproxy-linux-x86_64 server
2022/06/13 02:44:18 Starting up
WARNING: Failed to access redact from the internet
WARNING: Failed to access eredaxt from the internet
No admin domain set. Select an option below:
Enter ‘1’ to input manually
Enter ‘2’ to configure through TakingNames.io
So I made a subdomain manually and see that I have valid SSL certificates with cPanel. And I can access it on 80 and 443. So I can connect to the sub directory of /home/myusername/public_html/bpserver directory with ./boringproxy-linux-x86_64 in it.
But I still get
2022/06/13 22:43:18 Starting up
WARNING: Failed to access redact:80 from the internet
WARNING: Failed to access redact:443 from the internet
But when I make the admin domain set to bpserver i get this message
Enter admin domain:
2022/06/13 22:43:58 bpserver.yyyyy.xxxx: obtaining certificate: [bpserver.yyyyy.xxxx] Obtain: [bpserver.yyyyyy.xxxx] solving challenges: bpserver.yyyy.xxxxx: 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/586600566/97383089886) (ca=https://acme-v02.api.letsencrypt.org/directory)
Which is no surprise as I already have a SSL setup. If only we can move on and get the admin login allowed, along with the token as it dies now…I find no “login” code in the bpserver directory. I do find a boringproxy_db.json file with blank values.
Hi @DougK, I’ll need more details about what exactly your setup looks like and what role you’re wanting boringproxy to fill. If you can start a new thread with these details we can move the discussion there.
I have done that as asked.