Post 9y3ID6a6CooEvHOutU by Zambyte@fosstodon.org
(DIR) More posts by Zambyte@fosstodon.org
(DIR) Post #9y3G021tcM5T8K2blQ by bumbervevo@fosstodon.org
2020-08-12T16:21:57Z
0 likes, 0 repeats
anyone have experience with hosting a web server from home with Frontier as their ISP? I'm having issues getting port 443 to show up as open, even though nginx is listening. it's allowed through my home server firewall and being port forwarded from my router; trying to request an https page from my public IP throws out a connection refused error.
(DIR) Post #9y3G4zM2zTcWHipXIO by bumbervevo@fosstodon.org
2020-08-12T16:22:47Z
0 likes, 0 repeats
maybe a better question to ask would be, should I even consider hosting a web server on a residential ISP?
(DIR) Post #9y3G9i94OyKqMK0oFM by celia@fosstodon.org
2020-08-12T16:23:40Z
0 likes, 0 repeats
@bumbervevo Your ISP might be blocking your port. IF you can confirm that, use something like https://pagekite.net/
(DIR) Post #9y3GBBDTnkvuoLm7Fo by celia@fosstodon.org
2020-08-12T16:23:58Z
0 likes, 0 repeats
@bumbervevo Your ISP might be blocking these ports. IF you can confirm that, use something like https://pagekite.net/
(DIR) Post #9y3GC64aPUgh9H3Jo0 by Matter@fosstodon.org
2020-08-12T16:24:08Z
0 likes, 0 repeats
@bumbervevo yes, absolutely! The only true self-hosting is on a machine you control, so at home
(DIR) Post #9y3GlfaOMjIlQRtM0m by bumbervevo@fosstodon.org
2020-08-12T16:30:35Z
0 likes, 0 repeats
@celia that was my thought too, but it's strange because port 80 works perfectly from the outside. I think I'm just doing something wrong, but I'm having a hard time figuring out what.
(DIR) Post #9y3H02v6PIHhqhQyUi by celia@fosstodon.org
2020-08-12T16:33:10Z
0 likes, 0 repeats
@bumbervevo Can you look through your nginx logs maybe? You'll know if the request is reaching the server at all - sudo less /var/log/nginx/access.log
(DIR) Post #9y3ID6a6CooEvHOutU by Zambyte@fosstodon.org
2020-08-12T16:46:42Z
0 likes, 0 repeats
@bumbervevo I have used Frontier to host a web server, and I had no issues using port 443. Since you say you can hit 80 fine, I assume you have forwarding set up on 443, right?
(DIR) Post #9y3IU9jtiXhLdl7APo by bumbervevo@fosstodon.org
2020-08-12T16:49:48Z
0 likes, 0 repeats
@celia nothing about https requests in access.log or error.log. http requests are getting through though. I'll set nginx to listen for SSL on a different port and see if that works.
(DIR) Post #9y3IuN6mdMYEdJJtC4 by bumbervevo@fosstodon.org
2020-08-12T16:54:33Z
0 likes, 0 repeats
@Zambyte yup, port 443 is being forwarded to my home server. I have also have a Web UI for qBittorrent port forwarded, and checking that port from the outside works fine. I'll try setting up SSL on a non-standard port and see if I have any luck with that.
(DIR) Post #9y3J7Hhe2hNndIiciW by bumbervevo@fosstodon.org
2020-08-12T16:56:51Z
0 likes, 0 repeats
@Matter that's my thoughts, too. I feel like I'm wasting money by having really high up/down speeds and not doing anything with it.
(DIR) Post #9y3PBCxSE3dlneMqgK by kintaro@fosstodon.org
2020-08-12T18:04:47Z
0 likes, 0 repeats
Things I can think of : - Is your server block configuration correct ? Under /etc/nginx/sites-availables/ ? - Did you set the symlink from sites-available to site-enabled ?- Can you confirm (via logs ) that incoming connections to port 443 aren't dropped ?- Is there anything else like fail2ban or modsecurity that could block the access ?@bumbervevo
(DIR) Post #9y3PFzUfiG5bUOBYYK by kintaro@fosstodon.org
2020-08-12T18:05:20Z
0 likes, 0 repeats
Things I can think of : - Is your server block configuration correct ? Under /etc/nginx/sites-availables/ ? - Did you set the symlink from sites-available to site-enabled ?- Can you confirm (via logs ) that incoming connections to port 443 aren't dropped ?- Is there anything else like fail2ban, psad or modsecurity that could block the access ?@bumbervevo
(DIR) Post #9y3QLU33dfedeeS62C by bumbervevo@fosstodon.org
2020-08-12T18:17:53Z
0 likes, 0 repeats
@kintaro -I don't use the sites-enabled/available folders, I set up my own http folder and include any .conf files from that folder in the main configuration. server blocks are set up correctly because I can access them via http, and was able to get a secure connection with a non-standard SSL port.-https requests don't reach nginx; only http requests-this is a fresh install and the only network administration tool I've installed is ufw.
(DIR) Post #9y3QON5jxb9uwo5GZE by bumbervevo@fosstodon.org
2020-08-12T18:18:24Z
0 likes, 0 repeats
@kintaro -I don't use the sites-enabled/available folders, I set up my own http folder and include any .conf files from that folder in the main nginx.conf file. server blocks are set up correctly because I can access them via http, and was able to get a secure connection with a non-standard SSL port.-https requests don't reach nginx; only http requests-this is a fresh install and the only network administration tool I've installed is ufw.
(DIR) Post #9y4C2ayKT4szQTIdH6 by oldcoder@mastodon.oldcoder.org
2020-08-13T03:12:18Z
0 likes, 0 repeats
@bumbervevo Residential hosting of low-traffic websites should work in general. Usually, there are just the two obvious extra steps:(a) Set up port forwarding for TCP ports 80 and 443(b) Set up dynamic DNS for the domain names that you'd like to useFrontier does apparently block port 25, but I don't see reports related to port 443.
(DIR) Post #9y4C7MzHtDWxVA1Zrc by oldcoder@mastodon.oldcoder.org
2020-08-13T03:13:11Z
0 likes, 0 repeats
@bumbervevo Residential hosting of low-traffic websites should work in general. Usually, there are just the two standard extra steps:(a) Set up port forwarding for TCP ports 80 and 443(b) Set up dynamic DNS for the domain names that you'd like to useFrontier does apparently block port 25, but I don't see reports related to port 443.