cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problem when hosting with incoming https traffic

rlyness
Valued Contributor
Valued Contributor

I've hosted a football guessing website for a number of years on a dedicated server in my house (just for my friends for some fun).  I've had no problems until a few weeks ago when I renewed my contract with EE broadband.

Now, I am getting weird intermitting problems with some of the guys trying to connect to my website.  When they're on their home internet (different providers), they get a "Site cannot be reached ERR_TIMED_OUT" error - but when they drop off wifi and go on mobile internet, it magically just works.  To add, sometimes when I restart the router it suddenly works for a while then stops working again.

I've got a dynamic DNS set on my router so I know it's not a problem with routing.  It just, for some reason is not responding while on their home WIFI.  Also, it's not all users - some can access fine both on home WIFI and mobile.  It only seems to be https traffic affected, coming through on http fine all of the time.  My certs are valid, my port forwarding hasn't changed for years so I know all that is setup fine.

I've done a full factory reset of the router, I've temporarily hosted the site on a different machine on the network.  I'm all out of ideas.  Anyone had any similar experience?

25 REPLIES 25
rlyness
Valued Contributor
Valued Contributor

@bobpullen 

I de-activated the setting now but doesn't seem to have fixed it. The site is https://www.tenofthebest.co.uk

For some, it works on their PC, but phone on the same network it times out. Then, same phone, on mobile data, it works

rlyness
Valued Contributor
Valued Contributor

@bobpullen 

rlyness_0-1776871685250.jpeg

This is the screenshot I mentioned earlier.  It stayed like this for a while when I had loaded the app.  It stayed like this for a while until I went back in the app and it said it was then activated.  I de-activated and asked my friend to test his connection to the site and it didn't work for him.  I wonder would the router need a restart after this?  I did notice there were a number of blocked connections in the last 7 days before de-activating

rlyness
Valued Contributor
Valued Contributor

I came home after work and restarted the router with this setting turned off and it worked for about an hour and has not stopped working again

@rlyness - shouldn't need a router restart after the setting is changed but it's odd that it was stuck in that 'Activating' state for a while.

Seeing blocked connections is normal if you have any sort of server/service exposed to the Internet as it will attract a lot of unwanted attention. I get hundreds of these notifications a week.

When you view the notifications, it should tell you the IP address the traffic originated from and what it was trying to access. If those IPs match those of some of the problem visitors then it suggests you've found the culprit. It's all irrelevant though if the issue persists when the feature is disabled.

What is your server running on and have you checked the logs to for any evidence of these failed inbound connection attempts? Can you be condident that something's going wrong with them before they reach your server?

Kixy
Visitor

@rlyness have you tried resetting the App Pools?

rlyness
Valued Contributor
Valued Contributor

rlyness_0-1777138498202.png

Just to add to the further confusion here.  I use Whapi.cloud (they send a webhook to my server when a message is delivered on whatsapp).  In their control panel I can test the connection to my server.  You can see on my screenshot that it has delivered and accessed my endpoint on https successfully.  This is because I just restarted my router and tested it again - it will however stop working in the next hour or two with an error:

{"error":{"code":409,"message":"Internal Error","details":"Error: ESOCKETTIMEDOUT"}}

When the hostname or port is completely wrong , their service shows:

{"error":{"code":409,"message":"Internal Error","details":"Error: ETIMEDOUT"}}

I can't seem to trace any failed request logs on my server - doesn't seem to get through to IIS when it fails with these errors.  Is all this evidence pointing to a problem with my router?

rlyness
Valued Contributor
Valued Contributor

And as expected:

rlyness_0-1777217420114.png

 

RKYadav
Established Contributor
Established Contributor

Your website is opening fine on my EE Broadband and EE mobile data both.

--
RK Yadav
AI Frontend Engineer |
Previously contributed to EE Community under an earlier account @Rky.
That account is no longer accessible, so please do not send private messages there.
RKYadav
Established Contributor
Established Contributor

Last year I was facing some issues for instagram not working on EE broadband I disabled advanced web protection settings on EE router and this resolved the issue.

--
RK Yadav
AI Frontend Engineer |
Previously contributed to EE Community under an earlier account @Rky.
That account is no longer accessible, so please do not send private messages there.
rlyness
Valued Contributor
Valued Contributor

Thank @RKYadav - for the majority of our 40 players that is also the case.  There are a select number that cannot access the site when on home wifi - but works fine on mobile etc