i'm using rackspace server and just rebooted the server due to some reasons and after reboot i started the nginx service but now it shows 502 bad gateway
I already checked some error logs but still i'm unable to fix this issue
Related
I am running Ghost in development mode on FastComet hosting company. I dont know why but suddenly when i try to access my website I recieve the error
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.
If I do ghost restart it says that ghost is turned off, so it’ll turn on and everything comes back to normal. But after some minutes the 503 error comes back.
Does anyone now how can I find out the cause?
I am following https://github.com/bigchaindb/bigchaindb/blob/v2.0.0b9/docs/server/source/simple-deployment-template/set-up-nginx.md
I have Added SSL certificate to bleocean.com
and it was redirecting to my NGINX server page when i was reaching https://bleocean.com.
When I updated NGINX.config file to contents of https://github.com/bigchaindb/bigchaindb/blob/master/nginx/nginx.conf and did chenges as directed
It is now showing 502 Bad Gateway when i go to https://bleocean.com
I tried on local machine as well as on google cloud each time when I update config file it shows 502 bad gateway. Please suggest if I am making any mistake?
You are getting this error because there is no application running on the port 9984. Check if MongoDB, BigchainDB and Tendermint are running. Please add the logs of your /var/log/nginx/error.log.
I have been trying to learn AWS EC-2 and installing WordPress by Bitnami. I was planning to move all my sites from cPanel to AWS in the future if I could pull this off.
I am having issues with constantly getting 503 Unavailable Error when I attached the Amazon Issued SSL.
I was able to create an Instance, Certificate, DNS via Route 53, Load Balancer, Security Group and Target successfully I just can't get the site up. :(
Public IP works though 54.237.218.136
What could go wrong?
503 gateway time out it is. well your configuration and services need a restart , As Amazon provided Certificate works with Load Balancer (Application or Classic)
503 is the gateway time out from php-fpm or Apache 2 As you haven't shared the logs to give you a more prise solution I would suggest to login on your EC2-Wordpress powered by Bitnami and run the following commands .
sudo /opt/bitnami/ctlscript.sh status
sudo /opt/bitnami/ctlscript.sh stop
sudo /opt/bitnami/ctlscript.sh start
Please follow this document as well: https://docs.bitnami.com/aws/faq/administration/control-services/
I'm sure that committed changes with the configuration has not been loaded yet as your EC2 is even not responding on this IP ,
I'm sure about the Load Balancer and certificate is not the problem here.
You can ping me if you need help with this it's not a really tough job.
Thanks
I am trying to get GitLab setup with my current installation of Nginx but I keep getting an Error 502. I have included my configuration files, and not sure what I am doing wrong. But I followed the "Using a non-bundled web-server" steps on https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/nginx.md
/etc/nginx/conf.d/gitlab-omnibus-nginx.conf
http://pastebin.com/bQ8eCiNh
/etc/gitlab/gitlab.rb
http://pastebin.com/Lw5tjwXy
HTTP 502 means "The server was acting as a gateway or proxy and received an invalid response from the upstream server." So there are two possibilities here.
Your Gitlab server is not actually working or is returning an invalid response. After starting the Gitlab server, use sudo netstat -plnt and make sure it is running on a port and note the port. Then connect directly to this port in your browser (or from the CLI on the server if necessary) and confirm that Gitlab is working fine without a proxy in front of it. If Gitlab is running on a socket and not a port, there are also tools to test HTTP servers through socket connections that you can use.
Nginx is not configured correctly to connect to Gitlab. In this case, check your Nginx error log to see if there is any more detail besides the "502" error.
Locally deploying content between two site instances works fine.
It's when moving one instance to a remote server that gives me the following error message:
Module : login
Description : Remote user
Result : Error
Message : Connection timed out
My apache access log entries are:
./node_operations/deploy_now/86 HTTP/1.1" 302
./admin/build/deploy/logs/details/6 HTTP/1.1" 200
Deployment module version: 6.x-1.x-dev
Service module version: 6.x-2.2
Does anybody have an idea what could cause this problem?
Probably firewall is blocking if you are seeing timeout. You can fire up telnet on the dev box and test that you can actually connect to the target over port 80 - since deployment module uses xmlrpc to push content. If all is working there you can check the Drupal watchdog logs.