I got a problem with Nginx, it always shows "502 Bad Gateway nginx/1.2.1"
I am using Nginx on my Raspberry Pi with the software Piui.
Last time I used the pi it worked perfectly, now one month later suddenly it doesn't work. This is weird because I didn't change anything in the configs or in the Pi's system.
Does anyone have an idea?
I followed the PIUI Tutorial. Accesspoint works, can connect and ping from several devices.
I've searched for information, but can't find the issue.
As posted in the comments: Sounds like the sofware to which the request shall be proxied is not running, check if the piui-supervisor is running.
Related
I am using GCP, nginx and domain name from "name.com" to deliever my website.
It can be reached on mobile network but doesn't work with wifi.
Although on some wifis you can reach my site with around ~60% (from those i have tests) you cant.
It might have to do something with DNS / DNSSEC but its litearly a guess, I am clueless.
Hey everyone so I have found the problem.
When I looked online for best practice its recommended to use different ports for the backend and frontend.
apparently the port used for the backend was blocked by some routers.
Now the backend and frontend use the same port and it is fixed.
Hopefuly it will help other people who are getting the same problem.
Could you try lower the TTL to 300 seconds for your domain in name.com? It could be that DNS has an old cache which did not yet point to your nginx instance/location. Or you could wait out the default TTL which is probably 12-24 hours.
So I'm trying to setup my dev machine to be able to respond to some webhooks, as per the twilio documentation here:
https://www.twilio.com/docs/usage/tutorials/how-use-ngrok-windows-and-visual-studio-test-webhooks
I've got ngrok installed, and have the tunnel up and running, pointing at the port that is specified in visual studio. In this case, 44336.
However, if I go to visit the external URL, I get a very long load time, and eventually a 502 error. Visiting localhost works fine as expected.
So, I tried setting ngrok to point at 8080, and I get a little further along, but still no luck with the following error message in the browser.
With the first tunnel attempt, I can see the GET/ requests show up in the ngrok client, but no error. In the second attempt, I can see the 502 errors:
So I have two questions: How can I diagnose the source of the problem? And how can I setup IIS to accept connections from ngrok?
This is resolved in the latest version of ngrok (at this time 2.3.23).
A related closed issue can be referenced here: https://github.com/inconshreveable/ngrok/issues/448
You can now run:
ngrok http https://localhost:<port> -host-header="localhost:<port>"
for your example:
ngrok http https://localhost:44336 -host-header="localhost:44336"
Just go Right click on project -> Properties, and then disable ssl.
Check https://www.winsteadworks.com console for the error.
My website is on my raspberry pi 3 using nginx webserver to host my website. I am having trouble getting NAF (Networked AFrame) to work correctly. What I am trying to do is get Easyrtc to work correctly so I can interact/communicated with other players on my website. I got this to work correctly while it was hosted locally on my other computer, but when I moved it to the raspberry pi and tried to put it online was when I started to have issues.
I am getting a 403 error for my socket.io for easyrtc. On my website if you look in the console you will see the errors start to stack for socket.io.
What I have tried:
Check port forwarded ports
tried to add port 8080 to my config in /var/www/html/winsteadworks.com but kept getting errors
Checked my firewall settings for both my router and my raspberry pi
I also tried reconfiguring different files but still have had no luck.
The error:
socket.io.min.js:1 GET https://winsteadworks.com/socket.io/?EIO=3&transport=polling&t=MJ1pNxu 403 (Forbidden)
This error continues over and over every second and won't stop until you close the page.
I am at a loss here until I know a few things:
Why am I getting this error? Is this a nginx issue, is this an easyrtc issue, is this a raspberry pi issue, or is it a port forwarding problem (yes port 8080 is forwarded)?
What direction do I need to go in order to problem solve this?
Or I will just take the short, sweet and simple answer! Thanks in advance for you time.
I configured my gitlab instance with an external nginx server according this documentation and following nginx configuration.
All is working fine, but when i try to change some profile settings in the UI I get an connection reset.
The problem only occurs on multipart form POST/PUT operations.
The funny thing is, that there are no log entries in any gitlab log files, so i think there is a problem in the nginx configuration somewhere.
Please when someone has any idea on how to further analyse the problem.
Thanks
The problem was the MTU setting for the TCP-IP Stack on my windows machine. I switched from 1500 to 1300 and now all is working fine again.
To be clear, when I say "doesn't work", I meant that it returns a json object with a status of "REQUEST_DENIED". I always get a response.
I have a server key setup for the Geocode api, and I'm having an issue where it doesn't work with only one server. I've been using it locally (whitelisted my ip) without issue, and tested it with cURL on a Digital Ocean vps without issue.
On a WP Engine server, however, I cannot get it working. I've added the IP address and spent over and hour with their tech support verifying that it's the right address and there's nothing funny going on. They've used cURL from their command-line as well, but it doesn't work. I tried creating a new key just for that ip, and it still didn't work. I tried a 16-bit IP range, but no dice.
Can someone please shed some light on this? I wish Google provided a list of request IP's in the report so we could verify it's getting the expected IP. Is it possible that the IP was blacklisted by this point somehow?
Thanks!
Had a similar problem. Turned out I had to add the ipv6 to the allowed ips.