I have my website hosted on digital ocean on Fedora served with nginx. It was working fine this morning but now I'm gettin ERR_CONNECTION_TIMED_OUT. The server seems to be running fine as far as I can tell. I've restarted nginx, the website and the server numerous times to no avail. Pinging works, SSH into the server works, Curl to the wesbite on the server works, using the api as localhost on the server works. There are no errors in the nginx console. I'm completely at a loss, I don't find any reason why it shouldn't work. I checked the DNS settings with https://www.whatsmydns.net/ and everything's correct.
-> https://belgocanadian.com
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've been trying to port a standalone website I've been working on to WordPress. However, I haven't been able to install WordPress locally because MAMP isn't working properly.
I've installed MAMP on my computer fine. However, when I start the server and press "Open WebStart page", my default browser tells me "This site can't be reached. localhost refused to connect." I also noticed that there is only one green dot by MySQL Server; both the Apache Server and Cloud have white dots next to them.
I've tried a couple things with no luck. I've restarted my computer, but the same problem persisted. I went into MAMP Preferences and reset the ports to the default (8888 for Apache, 7888 for Nginx and 8889 for MySQL) but that had no effect. I've tried switching to Nginx, but kept getting 504 errors. Lastly, I've tried accessing the WebStart page in multiple different browsers with no luck, as well.
I'm running this on Windows 10 Professional.
Any help would be greatly appreciated. Thanks.
The issue is that you're probably trying to hit http[s]://localhost instead of http[s]://localhost:8888 ... your Apache port is set to 8888 so you need to tell the browser to look to that port. If you want to use the standard ports, you'd go to the "ports" section in MAMP and click the "Set server ports to 80, 81, 443, 7443, 3306, and 11211" option (or the equivalent). There's also the "Set server to MAMP ports" which moves all the ports back to 8888, 7888, 8890, etc.
I had the same problem, here's the fix that worked for me.
Launch MAMP stop the server then at the toolbar at the top press on MAMP-> ports then press set ports to default and then restart the servers it should work fine then.
Click on MAMP drop down, and click on preferences.
Then go to PHP.
Click on the Standard version drop down; and change it from 7.3.7 to 7.2.14.
Click OK.
Everything should be working fine now.
I'm having trouble getting my ASP.NET Core MVC web application deployed on Amazon's Lightsail hosting.
I've followed this article on Using Amazon Lightsail for ASP.NET Core to get my aspnetcore 2.1 application build into a service and nginx forwarding any accesses on the site from port 80 to port 5000.
My Lightsail instance is running perfectly fine:
From the SSH terminal, if I do a wget http://localhost, it returns an error saying there is no certificate. I have to force it with wget http://localhost --no-check-certificate, which then returns the index.html file for the webpage.
When going to the Static IP for my Lightsail instance on Chrome, however, nothing comes up on the webpage, saying "The site can't be reached".
If I had to guess what the issue is, it would be something about the certificate. I've searched around for solutions to that but found nothing of help.
What am I missing to get this application to run on the Lightsail Static IP so users can visit my website?
Did you open up the port on the lightsail firewall?
From your detail page for your instance click on networking and ensure you've added port 80
Also, try removing nginx and just accessing the application via port 5000 (after opening it up in the firewall).
I have first installed my WAMP Server on my personnal PC. It worked fine.
Then I pluged that PC in a network of a company (25 PC in total). I had acces to all there network. And I managed to make it work and accessible to everyone in the company but the WAMP is still on my computer.
To resolve that little problem, they got a Server with Windows Server 2012 installed. So I wanted to install my WAMP + DB, on this server.
So I installed correctly WAMP and MySql but when I go to the url that I put exactly the same on my personal PC, it shows me an error like : HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Like if the WAMP wasn't launched but I'm sure it is launched correctly.
Can this be a firewall issue ? Like an service bloking the port 80 (I guess ?).
Sorry but the network isn't my best subject.
EDIT
I found from where my error comes.
When I go to my url 10.13.48.60:80/my_page.php
In my error message, I see Physical Path C:\inetpub\wwwroot\
but thats wrong, it should just be Physical Path C:\WAMP\www\
How can I change that ?
I'm currently working on http://thomaskinkadegallery.com - however, now that I have set up a localhost (http://thomaskinkadegallery.com:8888) on my local machine, I cannot access the remote server anymore. I get a page timeout. I checked the page on another computer, it's working just fine.
What is blocking the site on my machine?