Search results

I’m still working through this stuff myself so that I would be able to access my NAS at home while I’m sitting at a Starbucks either down the street or 1000 miles away. Okay, so the next step is to do the ssl on my side. How should this be done ? Then install the reverse proxy? Then connect it...

So that basically means that even now when i am running the web app trough ip and port it is not that particularly safe? Secondly, if I choose to use the reverse proxy to "mitigate some of it" and not "all of it" as the info that they are actually enter is nothing like security IDs nor card...

What could that actually mean to me as a layman ?

Well I don't really care if my server is exposed as long as the information that is in there stays safe and will be accessible only by those who have the login credentials. The only thing that I want to do is for the users to be able to access the web app trough domain with https. The way with...

People who are accessing the current domain are complaining about me not using HTTPS (they are loging into the web app with their login info and exposing it) I know that I can not use HTTPS if I am not using a domain. Secondly, as I have already bought the domain name, it would be much easier...

Hello guys. I am currently working on a project where I would like to be able to access my web App N.1 (currently accessible only via IP:PORT) trough HTTPS and domain (https://www.example.eu/Application1) web App N.2 (https://www.example.eu/Application2) etc... To be honest i am pretty...