I'm sad

I was running a webserver on both normal HTTP and HTTPS ports.  My ISP is comcast.

Today I discovered the ports are blocked.  I feel like crying.

BEFORE:  www.yourgayfaggotsuckdicksite.com:80

AFTER:  www.yourgayfaggotsuckdicksite.com:5000

I was running a webserver on both normal HTTP and HTTPS ports.  My ISP is comcast.

If it is hosting content important to be public, it may be worth paying for a webhosting, or even a serverhosting service.

>>2
I know but now my friends at work that are behind hyper-restrictive corporate firewalls can no longer securely get their daily fixes using my self-signed certificate and HTTPS digest authentication.

I shall be doing that though.  I think I like port 44444...

>>3
Yeah but I like to test out stuff at home first, especially since I've been trying to learn fastcgi and stuff...

>>1
Have you asked the ISP why they blocked the ports?

find a better isp

>>1
Find a better isp before they shut you down for TOS vio.

>>7
Wouldn't they have already done that, if they were going to do th

owned

I have a problem with ISPs dictating what you can and cannot do with your bandwidth as long as it's legal: they're trying to turn a medium from one where anyone can be a peer to one where we're all just passive consumers.

Yay.

(´^ิω＾ิ)

>>4
That shouldn't mean any problem. I usually do the development work on localhost.