Recovering Wordpress link from pfsense


  • Hi guys,
    First time poster on this forum.
    Late last year, I installed pfSense on a dedicated box and because I didn't check my website, i just finally realized that I couldn't access my wordpress site, which is hosted on a separate box of mine, anymore.
    I used to be able to type in my main URL (lets say it's called mputtr.com ) and it would take me to my wordpress site. now it goes straight to the pfsense homepage.

    What can I do to reclaim the title so it redirects back to my wordpress site?

    thanks!


  • Move webgui to a different port, and enable reflection for the portforward you likely have on the wan?


  • How do i go about doing that?
    and once I move it to a different port, does the pfsense url change?


  • In System/Advanced you can change the webgui port i personally like 444 for that. And then yes the webgui url changes:  https://192.168.0.1:444/ or what your lan-ip is..

    As for reflection is a option of the portforward rule that might fix the issue of visiting the site internally (assuming your testing from lan network, to server on a opt network, forwarded from a wan-ip)


  • Ah ok, so I was able to re-direct the webgui and I did create 2 port forward rules for the ports. I left the NAT reflection to "use system default"
    I've attached a screenshot of my config. Am I still doing it wrong?



  • It depends what your system default is :)..
    There is no use masking 192.168. ip's b.t.w. as they are only valid on your local network anyhow..

    Under System/Advanced/Firewall & NAT check the following settings:
    "NAT Reflection mode for port forwards": PureNAT
    "Enable automatic outbound NAT for Reflection": checked

    https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks


  • I just tried that, still no dice.

    Does this mean I'll also have to somehow modify my wordpress settings? My LAN IP address has also changed from when I first had my wordpress site.. I don't know if that'll make a difference.


  • @mputtr:

    I just tried that, still no dice.

    Does this mean I'll also have to somehow modify my wordpress settings? My LAN IP address has also changed from when I first had my wordpress site.. I don't know if that'll make a difference.

    Yes it does. Easiest way is to do a database dump and a search for the old LAN IP address and replace each instance with the new LAN IP address. Notepad++ is your friend here. Once that's done restore your database and restart the database and you should be all set.


  • b.t.w. is the wordpress site running on 443 with https or on http :80 ?
    And make sure the browser aint doing some automatic cached hsts redirect..

    Whats the current effect of 'no dice' ? Browser times out? Shows any error wordpress page? Other?

    Edit..
    (Oké screenshot shows the forward being on HTTP :80 ..)


  • sorry i was vague.
    no dice meant it still timed out. It'll say site can not be reached. took too long to respond

    The wordpress site is using the default 80 & 443 ports.

    I did a csv dump of mysql database and looked for the old IP address but nothing came up. i think it's because I have it tied to my ddns so it would be something like mputtr.com rather than an ip address


  • If you currently visit the http://[WordPressServer-Local-IP-Address]/ does that work at all?
    Can you ping that ip, does it run a firewall of its own?

    The webserver that runs the Wordpress site should likely be able to respond when accessed through its IP address with 'some' webpage. If that doesn't work then dns probably wont help, and pfSense can do its best to forward traffic to a non functioning webserver, but that wont make it magically work either.


  • I tried directly typing in the IP address with the port #80 and i have the same issue.
    I tried to search the entire sql dump of the old IP address and nothing turned up.


  • So i guess at this point its more a Wordpress issue than one of pfSense. I know very little about Wordpress.. maybe Jailer can help, or perhaps the Wordpress forums would be a better place to start.

    Is Apache running on the Wordpress machine? Doe the logfiles of Apache show its starting properly and binding to the :80 socket?

    Once the Wordpress website itself works locally, then we can try and check further how to make it accessible through its dns name, and over pfSense's wan-ip.


  • hmm, maybe my wordpress setup is completely borked. I just tried to reinstall and it wouldn't even run the php file to do the initial install… I checked the apache log files but i don't really know how to read it.
    i'll probably have to try to start my wordpress from scratch and restore everything.


  • If you have it set up with a domain name then you won't be able to access it locally without NAT reflection.  Wordpress is rather finicky about that.

    I misunderstood your post and thought you had it running locally on your LAN and not exposed to the internet. Your port forward needs a little work. Change the destination to WAN address and your redirect target IP should be the local IP of your wordpress installation. Do the same for HTTPS and you should be all set.


  • @Jailer:

    If you have it set up with a domain name then you won't be able to access it locally without NAT reflection.  Wordpress is rather finicky about that.

    I misunderstood your post and thought you had it running locally on your LAN and not exposed to the internet. Your port forward needs a little work. Change the destination to WAN address and your redirect target IP should be the local IP of your wordpress installation. Do the same for HTTPS and you should be all set.

    You sir… are a magician.
    Now my main site works!!!!!!!
    i just have to figure out why my 2nd site doesn't work.. since it's just the same link with "wedding" as the host name. I'll have to see what else i need to change.