Recent Topics

Manage b2evo from multiple IP addresses

Started by on Oct 04, 2017 – Contents updated: Dec 01, 2017

Oct 04, 2017 01:22    

I'm just starting to set up my blog, so I'm still just using an IP address for access. I have entered my external IP address into my Apache 2.4 installation and my b2evo baseurl in _basic_config.php, and can reach it from the internet.

My problem: I am unable to access/manage the b2evolution from any machine on my internal network. My router does not support NAT loopback, so I can't browse to the external IP address and reach the web server. (The router uses micro_httpd and intercepts the traffic, so when I access http://67.x.y.z, it redirects to http://67.x.y.z/index.php. This file isn't on the router, it's on the web server, so I get a 404.)

So, what I want to do is administer the blog from my internal network, 192.168.x.y. I can set up the Apache server to listen on multiple IP's, but I can't figure out whether it's possible to configure the b2evo software to enable this.

At the moment, I seem to have two options: go to Starbucks and use their wifi to reach my blog, or reconfigure the Apache and b2evo with a private IP space to upload the next post. Is there a way to configure b2evo to use multiple IP addresses (one external, one internal)?


John Mc

Oct 05, 2017 05:46

Just to be clear: are you running your webserver on a machine at home for production use (i-e: not just for testing?)

Oct 05, 2017 06:08

And if yes:

1) for external traffic: set up a dynamic hostname with a dynamic dns service such as
2) for yourself: on your local machine hardwire that hostname to your local up by editing the hosts file

Oct 06, 2017 01:17

Yes, production use. I have domain name I was going to transfer once I had finished setting up/troubleshooting/etc. I assume from your recommendation, I will need to do that (or go with Noip, etc.) to make this work?

Not the answer I'd hoped for, but the answer I need--thanks!

Nov 18, 2017 03:39

Obtained my domain name and static IP; mapped them in DNS. Put the FQDN in both Apache httpd.conf and B2Evolution's _basic_config.php. Added a hosts file entry mapping the webserver's private IP to the FQDN.
I can now manage B2Evolution from the webserver and the site remains accessible on the internet.

Thanks again.

Form is loading...

blogging tool – This forum is powered by b2evolution CMS, a complete engine for your website.