Can't host my website on my linux server with my public ip only.Can't even ssh through it.lakshay.icu
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't host my website on my linux server with my public ip only.Can't even ssh through it.lakshay.icu
i have enabled port forwarding for port 22 and 80,disabled firewall,nginx is working properly.My website name is lakshay.icu. I have tried everything.What am i doing wrong
Do you have a business class plan? I know here in the states the average ISP doesn't like us running servers on home connections. Most ports are blocked in their stuff, doesn't matter what ports you open on your own router.
Do you have a business class plan? I know here in the states the average ISP doesn't like us running servers on home connections. Most ports are blocked in their stuff, doesn't matter what ports you open on your own router.
it allows every port to be accessed locally and there is not business plan
which is meaningless, there's nothing in a generic ISP router that would block ports internally via wired connections.
Quote:
Originally Posted by Lakshay99
and there is not business plan
Ok, so you may find that all inbound "fun" ports like 22,80,443 are blocked by your ISP to stop people hosting public facing systems on their residential service (this would also be backed up by the fact that it looks like you're within a DHCP range).
Your external DNS is definitely screwed up as it's resolving from 8.8.8.8 as a 172.16.X.Y address.
The other address you mention 103.206.100.251 doesn't respond to ICMP ping, that may be intentional by you if you've disabled ICMP, although I doubt you set that up. So may be your ISP blocking at least that type of traffic.
You don't mention what your router is, if it's an ISP supplied one or your own.
One thing to be aware of is that if your IP shows up in a "residential" block then it's possible that many mail servers will reject e-mail you're trying to send. Especially if you're in a "known spam" country like India (sorry, blame the many, many spammers and 'Amazon Prime' scumbags that operate there).
which is meaningless, there's nothing in a generic ISP router that would block ports internally via wired connections.
Ok, so you may find that all inbound "fun" ports like 22,80,443 are blocked by your ISP to stop people hosting public facing systems on their residential service (this would also be backed up by the fact that it looks like you're within a DHCP range).
Your external DNS is definitely screwed up as it's resolving from 8.8.8.8 as a 172.16.X.Y address.And also can you tell me what changes do i need to make in order to successfully host my website
The other address you mention 103.206.100.251 doesn't respond to ICMP ping, that may be intentional by you if you've disabled ICMP, although I doubt you set that up. So may be your ISP blocking at least that type of traffic.
You don't mention what your router is, if it's an ISP supplied one or your own.
One thing to be aware of is that if your IP shows up in a "residential" block then it's possible that many mail servers will reject e-mail you're trying to send. Especially if you're in a "known spam" country like India (sorry, blame the many, many spammers and 'Amazon Prime' scumbags that operate there).
After you've fixed the DNS entry to point to the your external address, double check that the router is forwarding port 22 to the right system on your internal network.
Then if your ISP, Tenda, is using DHCP then you might have to also look into using a dynamic DNS service, either from your registrar Namecheap or somewhere else, to point to but that would come after figuring out basic connectivity.
After you've fixed the DNS entry to point to the your external address, double check that the router is forwarding port 22 to the right system on your internal network.
Then if your ISP, Tenda, is using DHCP then you might have to also look into using a dynamic DNS service, either from your registrar Namecheap or somewhere else, to point to but that would come after figuring out basic connectivity.
I have done everything you said but i don't think it is working
Your DNS entry seems to point to an IPv4 address in a netblock managed by NetMan Data Services:
Code:
$ dig lakshay.icu | grep -A1 'ANSWER SECTION'
;; ANSWER SECTION:
lakshay.icu. 1772 IN A 103.206.100.251
So that step is completed.
However, is that the actual external address of your router or are you behind several layers of carrier grade NAT? Please log into the admin interface of your router from on your LAN and check what it says it has for an external address. If it does not match the above DNS entry but instead has something in either 10/8, 172.16/12, or 192.168/16 then you can't get there from here and will have to negotiate something with your ISP or else set up an Onion service.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.