bjorn Posted December 31, 2019 Share Posted December 31, 2019 Hi, I'm using letsencrypt to subdomains to a few of my dockers. I would like to point the "top domain" to a web server where I can edit the site. How would I do this? Do I need to install a server or does letsencrypt have one I can use by default? Maybe I'm using the wrong phrases but I can't find anything. Sorry for the bad english, I'm tired and english is my second language. Quote Link to comment
RossEm Posted December 31, 2019 Share Posted December 31, 2019 (edited) hey! In the config folder of your let's encrypt should be an www folder. There you should put all of your web files. You should also disable the ONLY_SUBDOMAINS variable. The ports of your let's encrypt should be 1443 local and 443 public, 180 local and 80 public Edited December 31, 2019 by RossEm Quote Link to comment
bjorn Posted December 31, 2019 Author Share Posted December 31, 2019 1 minute ago, RossEm said: hey! In the config folder of your let's encrypt should be an www folder. There you should put all of your web files. Ah yes, I've found this folder. I don't know how to access this folder through my domain outside my network though. The domain itself is also pointed towards the correct IP-adres but it doesn't find anything. Quote Link to comment
RossEm Posted December 31, 2019 Share Posted December 31, 2019 (edited) Can you acces it via your public ip? https://PU.BL.IC.IP Edited December 31, 2019 by RossEm Quote Link to comment
bjorn Posted December 31, 2019 Author Share Posted December 31, 2019 3 minutes ago, RossEm said: Can you acces it via your public ip? https://PU.BL.IC.IP No, I just realised that when I add ":443" after the domain I get a different error message. So it seems like I'm accessing some server. 400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.16.1 Quote Link to comment
RossEm Posted December 31, 2019 Share Posted December 31, 2019 You need to put ONLY_SUBDOMAINS on false. Quote Link to comment
RossEm Posted December 31, 2019 Share Posted December 31, 2019 can you send a screenshot of your configuration? Quote Link to comment
bjorn Posted December 31, 2019 Author Share Posted December 31, 2019 Same error as before Quote Link to comment
bjorn Posted December 31, 2019 Author Share Posted December 31, 2019 33 minutes ago, RossEm said: can you send a screenshot of your configuration? Seems like it works when I add "https://" in front of it. Do you know if there's a way for me to make it work with only the domain? Quote Link to comment
RossEm Posted December 31, 2019 Share Posted December 31, 2019 is there an option in your dns provider to send all traffic to https? Quote Link to comment
bjorn Posted December 31, 2019 Author Share Posted December 31, 2019 10 minutes ago, RossEm said: is there an option in your dns provider to send all traffic to https? Hm. I'm gonna talk to their support. (Namecheap) Quote Link to comment
bjorn Posted December 31, 2019 Author Share Posted December 31, 2019 (edited) @RossEm They were'nt able to fix it however I forwared both port 80 and 443 to my internal https port whiched solved the problem. Can't really think of any disadvantages of this at the moment. EDIT: Thanks for the help and the quick answers by the way. Happy new! Edited December 31, 2019 by bjorn Quote Link to comment
RossEm Posted December 31, 2019 Share Posted December 31, 2019 hey thanks! glad to help! Quote Link to comment
RossEm Posted January 4, 2020 Share Posted January 4, 2020 hi! happy new year, You need to change some settings in your "default" file inside appdata/LetsEncrypt/ngix/site-confs you should add/edit this to the top of the file server { listen 80 default_server; listen [::]:80 default_server; server_name _; return 301 https://$host$request_uri; } Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.