My Let's Encrypt certificate has also now been fully verified, so it must be something like a permission or hostname issue. To provide some extra information which may help, here are my DNS records (with sensitive info crossed out): Update:īypassing Cloudflare's proxying brought the same result - a 403 forbidden. I don't change anything else.įor the time being, I have just switched my site back to http so it is accessible, until (hopefully) this issue can be solved. Abyss Webserver alternatives are mainly Web. Other great apps like Abyss Webserver are nginx, Apache HTTP Server, Caddy and lighttpd. The best alternative is XAMPP, which is both free and Open Source. All you have to do is to follow the on-screen instructions. There are more than 25 alternatives to Abyss Webserver for a variety of platforms, including Windows, Linux, Mac, Self-Hosted solutions and BSD. If an old version of Abyss Web Server is already installed on your computer, you may be asked to uninstall it. Double-click on the software package icon. Like I said before - when I switch back to http on port 80, everything works fine. Open the directory where you have saved the software package. The documents path htdocs/ has never changed and is not in a position that requires elevated permissions to access on my computer. To prove I followed the instructions correctly, here are what the main settings for my site in the main console look like (with my hostname):Ĭould it be some rule on my computer that I'm unaware of? It's a serverside issue I think, not anything to do with cloudflare. So when you visit my site, it will say https, but this is only between the user and Cloudflare - the traffic between my server and Cloudflare is still plain old http on port 80. And the console is showing that everything is fine, when it's not.Īll my web traffic goes through Cloudflare before reaching me - could that be what's causing the issue? If so, I'll just stick to http with Cloudflare, because of the extra security they provide, but this sounds like something that is wrong with my pc - something is not allowing https requests to actually access the website.Ĭloudflare provides some encryption by themselves, however this is just between the user agent and the Cloudflare servers - there is none between Cloudflare and the origin server. No issues were encountered when generating the LE certificate. And the only thing I'm changing when switching from https to http is the dropdown box that says protocol (see the image below) then restarting the server.Ĥ43 is obviously open on my computer and router (otherwise I'd just be getting a timeout response) When switching back to http, there are no problems - I can access the site perfectly fine. Abyss Web Server is a easy to use and feature rich Web Server. I followed all the instructions found on their website exactly, but when trying to access it afterwards, it just gives a 403 error. Information on how to configure the FastCGI support for the Abyss server. I'm running Ubuntu server 20.04 with Abyss Web Server, which has native support for using Let's Encrypt certificates. I want traffic on my web server to be served securely.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |