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?
Related
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 have been trying to integrate strip payment gateway system. Everything working perfectly fine on localhost. But when i uploaded to the server it does not work.
Are you running it in HTTPS?
Is the rest of your frontend/backend working properly communicating with eachother?
Are you getting any errors?
Stripe Forces HTTPS for all services using TLS (SSL).It is like their requirement that must be fulfilled. Please Have a look Here.
So in order to make it work on a server, SSL should be installed on that server to work with Stripe.js libraries. In addition, all pages should be served over HTTPS. Further readings.. Here
I am trying to redirect my meteor app (hosted by heroku) to www with https on. So:
https://exampledomain.com -> https://www.exampledomain.com
Is there a way to do this either in Heroku or the Meteor application itself? Thank you.
Meteor by itself cannot do redirects and does not support https.
Heroku is a hosting service, and will host whatever compatible application you give it, on top of it's Cedar stack, which is basically an Ubuntu OS. It does not even know that your app will be using http. So the Heroku environment will not help you either.
What you need to do is build an Heroku app consisting of your Meteor app and a HTTP Reverse Proxy in front of it, which handles the redirect you are asking for, and also the https. This proxy terminates the https connections coming from the Internet, and serves them as http to your Meteor app behind it.
The easiest proxy to set up is Nginx, although HAProxy also works well.
Have a look at for example Have you managed to make your node nginx proxy setup on Heroku work? for how to set this up.
I am applying SSL in my sample web application using self signed certificate. The purpose is to test the session availability when I go from http to https or the other way round.
My localhost address is localhost:5366. I have done these as follows:
I have added a website in IIS. But confused that when binding using http, I give port 5366. I works fine but when I remove it and apply https, port 5366. The page doesnot load.
So, what should I do to accomplish this?
Its a bit confusing, but if i can bet, you are interchanging the debug mode from VS and the published site, correct me if am wrong.
I configured my https site in this way:
Configure your IIS to accept https through port 443.
Set the website file system place to a certain folder
Publish your website with VS to this folder
Reach it through https://localhost
Hope it works!
My project was not residing in the iis physical path. Therefore, it was not loading my desired pages. Thank you guys.
I have published ASP.NET web site, using IIS7 on Win7. I can access this web site on my localhost, but it is inaccessable from other computers via internet. I have tried to disable firewall and anti-virus program, but with no success.
Does anyone know what may be causing this problem?
It works fine if I publish it on winXP.
Try checking out your router settings for port 80 forwarding;
Check out information about your internet provider as well;
There are providers that block port 80 outgoing traffic.
Try checking to see if the website is actually bound to 127.0.0.1. If it is, it would work for you but no one else.
Try to hit the website from a different computer on the internal network. If you can't hit it internally, then it is an issue with the local configuration on the webserver. If you can hit it internally, but can't hit it externally, then there is some kind of routing issue from the outside.
Its likely a routing issue from the outside, so think about these steps:
External DNS
Proper NAT/Firewall settings
Try using telnet to connect to the website and see if you get a response
Use tracert from the outside to see where the traffic is failing (if its failing)
Check the security settings on the deployed folder and check "Everyone" has read access. If you've not deployed under wwwroot they may not