Hi
I have a LAMP webserver built on a RaspberryPi. The Wordpress website is on a static ip at 192.168.1.159 and loads perfectly. I cannot get the ports 80 or 443 to open up on my RUTX50 to be able to access the site from the web. The domain name is
www. davidhallows.com
this points to https://davidhallows.duckdns.org which points to my public ip
I’m not sure by what exactly you mean by default route? I SSH into it on that IP, the wordpress website is set to deliver on that IP too. I don’t think it has an SSL certificate yet, if that would affect the port opening, I didn’t think it would?
No, SSL should not affect this.
I mean, when you ssh into raspberry try to execute ip route command. There must be line like this: default via 192.168.1.1 dev.......
I’m very new to mobile connectivity and i may be wrong but i think you cannot do what you are trying to do.
When you are connected via a mobile device you are given a public ip address that is shared with others. Many users share your public ip address, the network you’re connected to adds another layer giving those users sharing a public ip address another ip address which inaccessible to others on the wider www.
You’re pointing traffic to a public ip address behind which there could be many devices and the network has no idea which device to send the request too on that subnet.
You live in a block of flats, say 200 flats, numbered 1 to 200. The block of flats has an address. I send a letter to that address, but the letter does not have a flat number or the name of the recipient written on it.
The letter is delivered to the front door, but nobody knows which flat to deliver the letter to, so it doesn’t get delivered, somebody eventually throws it in the bin!
To do what you’re trying to do, i think that you need a static public ip address and a second mortgage!
Do you have multiple connections to the internet? Mobile SIM1 & SIM2, or and via the WAN port onward to some other service such as a landline, fibre, satellite, radio etc etc.
When i ping your dyndns address, the response gives me an EE LTD IP address, which suggests that your connection is a Mobile connection. You share your dynamically assigned public IP address with dozens, hundreds, perhaps even a few thousand other peoples devices in your neighbouring wider district. Many EE customer devices in your neighbourhood will have the same outwardly facing public IP address as you.
The EE network can’t and won’t connect you to your device from the wider web.
See image below, my EE dynamically assigned public facing IP address is “31.94.32.194” which i share with everybody in my neighbourhood who is with EE. This may not be strictly correct, but i will be sharing it with a lot of other EE connected devices somewhere. My RUTX50’s IP address is “10.78.77.182”, this IP address is unique to my router. Your request to get to your router is being blocked either by BT or by EE.
When i run the traceroute command on your ip address i get stuck / blocked at hop number 6 which is a BT address somewhere long before i get anywhere near your public ip address.
Yes, it does sit on a mobile sim carded router. I understand form your generous answer my predicament. I have just signed up to pagekite which seems to have done the trick perfectly.
Many thanks for pointing me to the right line of query, much appreciated.
