How to change tunnel location and can't access locally
Hi, I just installed coder via the CLI and have two problems.
1. It always defaults to "US East Pittsburgh", which gives me a high latency, as I am in Germany.
2. I can't access it via IP:PORT, but don't know why.
Yes the IP and port are correct and I am in the same network, but it just doesn't work.
16 Replies
<#1371064755615305828>
Category
Help needed
Product
Coder (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
And as said, accessing
http://192.168.178.170:3000/, just doesn't return anything.
hell, you need to host it on your own domain to get rid of the Coder tunnel in Pittsburg
try.coder.app is in the US but it's only meant for testing purposes
But shouldn't I still be able to access it locally?
I just went with the quick start guide
Where it also shows it being accessed locally after the same steps I did
yeah but when you have the try.coder.app tunnel enabled it won't start one locally
Ah okay thanks, but could I also just disable tunnels entirely?
Also even with a custom URL and a CF Tunnel I still can't access it locally or remote
you can, but you don't want to
what I'm referring to as the 'Coder tunnel' is the try.coder.app proxy, and that is disabled by defining an access URL
could you share a bit more details? (screenshots, logs, etc)
Sure thing. Just to be sure I started with a fresh VM and installed nothing besides coder. Then added the domain entry to CF Tunnels. But even still, I cannot reach the site locally either
ip a entry stayed the same
https://discord.com/channels/747933592273027093/1371064755615305828/1371065228191858799
Anything else you need?
Also tried changing the HTTP listener address to 0.0.0.0:3000 and 192.168.178.170:3000, but same result
Now it's all default except the access url
Also no ufw or any other special stuff running
Just tried doing a curl 127.0.0.1:3000 from the VM itself and that returned something. So it's really just somethingh about me not being able to access it from any other device
I am lost. I just tried the exact same thing again:
coder server --access-url=https://code.pyenb.network/ --http-address=192.168.178.170:3000 and now it just works??
I will take that. Thanks for the help anyways
nvm. It's still not working via Domain. I can access it locally now, but the domain stays blank:
https://code.pyenb.network/
It sometimes works, but then throws a 404 in the next second
Could be DNS tho
imma seeProblems seems to persist. Healthchecks keep failing. If I refresh the websocket one, it keeps switching between 101 and 404
what's your config?
@Pyenb
ok I see what happen there, should use a coder.env to run it locally for consistent env var
I have a script like this:
I used to run it like this (now I run coder behind reverse proxy in container)
when you specify access_url I think you have to specify key/cert files as well ( correct me if im wrong), but run without tls enable is totally possible. You just drop tls_enable=false, and coder will ignore coder_http_address i think
then point your CF tunnel to http localhost:7778
works with coder in the past, I havent playing around with coder without tls enable for awhile so I'm not sure if it worked
without tls enable coder prone to break if CF decide to timeout
I suggest grab cert/key files and enable tls
if you don't know how to use reverse proxy/letencrypt/certbot then just use ssl cert/key generated by cloudflare (assuming you have your domain registered to cloudflare?):
Yeah, just was testing around. Ran it via systemd otherwise
That was the idea, as CF should do the automatic TLS stuff
okok, thanks
Not registered, but I use it for DNS