I have project developed in Node + react combination. We have deployed it on aws. But from last some days site stopped working. I have checked domain but i didnt find any issue with domain. Actully when I checked with terminal I noticed that I didnt receive any request from client side when I hit the website from browser.
So I checked with nginx status but its showing me failed. I have attached image which shows nginx status. Can anyone tell me how I can make nginx up and running again. I am completely new to handling server things. So I dont have that much knowledge about it. Thanks in advance
Related
Setup: I use a self-hosted code-server (dockerized) behind a fritzBox on my home lan. I have a FQDN (mysub.mydomain.com) pointing to a dyndns (mysdyn.my-router.com) with a cname entry which ends up on the fritzBox, port forwarded to the docker machine via a nginx reverse proxy with letsencrypt enabeld.
code-server works fine and is available via mysub.mydomain.com. With the live-server plugin works great#code-server and can be reached via mysub.mydomain.com/proxy/3000/ (3000 is an example port). Hot-reload and Javascript works.
Problem: working on a nuxt.js project (universal), when I run "yarn dev" the dev-server comes up normaly and the page can be reached via mysub.mydomain.com/proxy/3000/ and displays correct. But the "hot-reload" as well as all java scripts are not working because of a 404 for all .js-files.
The browser is looking for all .js-files under e.g. https://mysub.mydomain.com/_nuxt/runtime.js which correctly causes the 404, because coorect location would be https://mysub.mydomain.com/proxy/3000/_nuxt/runtime.js
What is causing this behavior and how can I fix this? I am even not sure where to start. Nginx or Nuxt? I already tried to play around with the router-setting in the config.nuxt.js - no luck.
thanks for your help!
So, mysub.mydomain.com/proxy/3000/ is a hosted website behind an Nginx configuration?
If it's the case, you can't use yarn dev. This command is aimed towards a local development server.
You can't have HMR running on a hosted production app through some DNS, reverse proxy, port forwarding and so on. Or at least, this is what this is aimed towards.
Even having hot reload via code-server is kinda not mainstream. So yeah, you could maybe try some hacky things and achieve it, but you'll still end-up experiencing quite some bugs and the performance will probably be sub-par.
You don't want to stick to some local running apps?
I am not a backend server guy, mostly work the front end(design and Javascript work). So pardon my beginner questions/terminology. But I could really use some help! Due to covid I am working remote and this is just NOT my expertise.
I have 6 sites I work on locally via a local environment (Nginx, virtual box). Recently, out of nowhere 1 of the sites has started redirecting to an HTTPS version and it will NOT load on any browser due to "ERR_SSL_PROTOCOL_ERROR", so I can not work on that site as of now. All the other sites, that live in the same environment, load fine and are not secure versions.
I have looked at their config files and they are all the same. I don't understand how 1 site is NOW getting redirected to an HTTPS version, I never get into the Ngnix system to change things. And unless I'm missing something it's my local env so nothing could be introduced from the outside.
Questions: Can I just redirect it back to the HTTP version??? OR can I add some certificate to fix my "ERR_SSL_PROTOCOL_ERROR" error?
Any help or direction would be greatly appreciated and the gods will shine upon you.
I'm getting a strange behavior in my stack that I don't know where to look.
Using WordOps default install on Ubuntu 18.04, running on a VM Instance on GCP.
WordOps installed Nginx, php-fpm, MariaDB, WP and Redis cache out-of-the-box.
Initially, everything worked just fine. Then, on my phone, I started getting nginx 404, but on my pc it works. Sometimes the initial page doesn't work, but if I go to wp-admin, the page loads normally.
It is more strange that, on some devices, it works, it others it doenst, returning 404 page.
I really don't know know what's going on.
Anyway, the URL is www.lindastore.co.jp
The problem was with Let's Encrypt SSL certificates. Not sure why, but clearing then re-issuing fixed the problem.
I have a web app that used to run on IIS at http://localhost:3878/Admin; however now for some reason I get this error when I try to access it in a browser:
This site can’t be reached
The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_RESET
Why would I be getting this error all of a sudden when the app worked earlier today? I checked in IIS to make sure the app is started. The IIS logs are not showing any requests to this app. Event Viewer shows a compile error related to this app (I tried to access an include aspx page directly from the browser; I want to fix that issue with the web app where it's displaying the source code from the aspx pages that are used in #include statements) but that shouldn't take the app down once and for all should it?
If someone else face ERR_CONNECTION_RESET with http. Then you could try https first. If https binding fix the problem. It would help narrow down the root cause.
You may need to check whether require https has been enabled or mistake. In some case, enable https or HSTS in project will cause ERR_CONNECTION_RESET.
Of course, enable https would be considered as a workaround.
I have an ubuntu 14 server running nginx. I use it for a WordPress website
Out of the blue for no reason the php5-fpm shuts down automatically (I am not sure it even is called shutdown, I get the nginx error page).
This is the message I get now on my site::
An error occurred.
Sorry, the page you are looking for is currently unavailable. Please
try again later.
If you are the system administrator of this resource then you should
check the error log for details.
Faithfully yours, nginx.
I restarted the php5-fpm from the command line and my site goes up for 30-40 seconds and then it goes down again.
What can be the reason? How can the php5-fpm decided on itself to do this? If it helps I'll add that this is a digital ocean server
Thanks upfront!
I faced the same problem, Click here! to solve.
Its because your resource was fully utilized by xmlrpc.php. Possibly Brute force attack.
Block access to xmlrpc.php in nginx config.