#Unable #Connect
Big Tech is making its stuff slower and stupider — on purpose
#Big #Tech #making #stuff #slower #stupider #purpose
#Big #Tech #making #stuff #slower #stupider #purpose
#Judge #halts #Voyager #Digitals #bln #sale #Binance.US
#Yesterday #HUGE #day #moons #completed #moons #pizza #trade
#Nitrous #Users #Airbnb #Bleach #Powder #questions
#cryptocurrency #subreddit #allowed #control #supply #moons #banning #people
Hi!
Just to cover some common pitfalls:
On the same system that’s running nginx, do these curl requests return any HTTP response code (200, 404, 5xx, etc.)?
curl -v http://127.0.0.1:81/
curl -v –resolve [onion-hostname]:81:127.0.0.1 http://[onion-hostname]:81/
(replace [onion-hostname] including the brackets)
Any response (even a 404) is good enough here as it will at least prove nginx is running and listening on port 81. If you’re listening on a new interface for the first time (like TCP port 81), nginx needs to be restarted; not reloaded.
If those all work, be sure your testing URL has the non-standard port defined, otherwise the browser will try port 80 and fail (since you’ve set the onion service to listen on port 81):
http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion:81/
(the above onion is just for demonstrative purposes only)
You should be able to keep listening internally on [127.0.0.1:81](https://127.0.0.1:81) and accept connections on the typical port within Tor by setting `HiddenServicePort 80`
Works for me with obfs4 bridges
> Sudo Tor
Do not tun Tor or other programs that don’t need it as root!