ACT Fibernet Static IP is anybody else here using static IP from ACT fibernet?

Hi everyone

I am from Hyderabad. I requested static public IP to host my website.

They claimed my ip series start with 49.xxx.xxx when I looked up online on whatismyip.com

However I can not ping that IP or nor I can bind it with my apache server.

Its really frustrating. I called the customer care service and ask them what is my static ip they says 10.xx.xxx series.

They are insane. I just got mad. how nat IP can be my static IP. static IP cost 230 Rs per month I agreed for that. I still cant' bind my server nor I can ping static IP.

I just don't know what to do? anybody else here using static IP from ACT fibernet?

I'm from Chennai and using static IP allocation from ACT - but it's a bizarre setup, so allow me to explain:

For some reason, they're NATing the private IP allocation given to you, with a public IP address. For instance, that 10.x.x.x IP address given to you is attached to a particular public IP address. The only difference here, is the allocation does not 'end' at your router level like it should. Instead, your router is setup with the static private IP address (10.x.x.x) whereas it translates to the public IP in the backend of ACT.

In my case, I wanted them to give me an actual public IP, not this NAT crap - nevertheless, it still works as expected, just not explained properly by them in the first place.

In your case, I assume your apache server is behind a router, so you should be binding the local IP address that's allocated from your router to the apache box - not the static that's supposed to be setup in your router, nor the actual public IP that's displayed on whatever site you check.

So the setup should look like this :
Router (with a static WAN on 10.x.x.x) --> Port Forward (assume you want port 80) --> Apache server (bind to local IP given by the router, ex 192.x.x.x)

If you visit the public IP address (ex to check from whatismyip.com) directly from another connection, your apache server should respond. Likewise, pings will respond, as long as your router is setup to reply back and not just block. Some routers won't reply ICMP pings unless specifically configured to do so.

TL;DR:

Static IP from ACT means getting a static 10.x.x.x IP address, which will translate to a public IP address - this does not change, so technically it is still static except it's setup this way.

Hi All,

Request you to share your Customer ID or registered contact number and we will get back to you.

Regards,
ACT Fibernet

Hi the problem is solved. I realised its a simple mistake. But its because the static IP is not directly assigned to my network adopter. This is the reason Its getting blocked from windows firewall. I am not using a router.

Before ACT, beam assigned direct static IP to network adopters its worked perfectly without its getting blocked by windows firewall.

If anybody getting this kind of problem and can not ping ip. Just allow port 80 from your windows firewall or any other firewall if you use third party firewall. it works.