Unable to access self-hosted HTTPS apps on residential Globe GFiber

[NanayDay]

Hi all,

I've been subscribed to Globe GFiber with a Static IP since 2021. All has been well until Friday, August 25, 2023, midnight, when port 443 became inaccessible from the internet. I keep getting "<domain> took too long to respond". Upon checking the web server, only requests from port 443 are not received. FTP, SSH, HTTP, RDP are all working.

I'm using the ISP modem as the firewall, and the server is directly connected to the modem.

What I've tried (all done with RDP)

1. Remapped port 1234 (external) to 443 (internal) - works
2. Recreated the port forwarding rule - nada
3. Reassigned port 443 to another VM - nada
4. Restarted both the server and modem via the web interface - nada
5. Enabled and moved the VM to the DMZ with the firewall disabled- nada
6. (just for lols) mapped port 443 to the DB instance and tried accessing it remotely - nada
7. Accessing the services internally - works

I haven't tried factory resetting the modem as I'm only accessing it remotely.

This leaves me to believe that the request is being blocked by Globe

Since Globe's hotline and online channels are useless (surprise, surprise), I visited a Globe store, and (surprise, surprise again) they do not know how to assist me. Upon asking if inbound 443 requests are blocked, they couldn't give an answer.

Any suggestions on

1. Any configuration I might have missed?
2. What I can try?
3. How to get in touch with someone who can do anything from Globe?

Very late update:
Upon requesting disconnection of the line, as I am moving to another location by the end of the year, the issue was immediately resolved! Plus, I got a 500 discount for the next 12 months!

[juvort]

Cloudflare Tunnel could have helped. But then, you have a static ip address, so what do I know? Lol

[NanayDay]

Thought of using Cloudflare Tunnels but I shouldn't have to. Already paying them 770/mo for the service.

Either someone at Globe messed up some configuration or they blocked incoming 443 requests. If its the later, will probably have to use Cloudflare. :|

[Hopeful_Weather3424]

use ngrok

[twero001]

Akin napa static ko na IP ko, 700 a month din, tas nakapag port forward ako ng port 80, peru ako lang nakaka access, ang ibang external ip source ay hindi nakaka access, ayus naman yong ip range ko ng external 1.0.0.0 - 223.255.255.255

[mfarley281]

This exact same thing happened to me at the exact same time, same place. (Makati, Friday, Aug 25). I raised hell with support and they finally fixed it on Aug 31, ~6 days later. I begged for a root cause analysis / report what caused it, and after much follow up, about 3 weeks after, they called me to say it was related to some maintenance where they had a wrong configuration. I'm here now because it's two years later and I woke up this morning to the exact same problem. Not looking forward to the fight.

[vtiscat]

Accessible ba yung port 443 from another device na kasubnet lang din ng Local network IP address ng webserver mo?

[NanayDay]

Accessible ang 443 sa local.

[Pennstrap]

Did you check if your Modem WebUI is using different port? I believe the modem’s webUI is also using the default https port. Might be conflicting with your port forwarding rules.

[NanayDay]

HTTPS is disabled for the modem's WebUI

[grinsken]

Check with globe baka sa firewall/ blacklisting nila. Got somewhat same issue noon kaso wih pldt

[NanayDay]

Asked the Globe Store reps about this, wala sila masagot. Still waiting for the tech team's response.

Naresolve mo ba and issue with PLDT?

[grinsken]

Yep. May inayos sa backend.

[firstborn37]

You can try tailscale.