Intranet - Wordpress behind Smoothwall

[chinesewhispers]

I'm trying to set up a wordpress site as our intranet. I've got this far:

 

- installed Ubuntu 14.04 VM

- updated Ubuntu

- installed and configured LAMP

- downloaded and installed Wordpress

 

Everything has been OK so far, a bit of a learning curve for a non-Linux user, but good up to here.

 

Now the problem appears to be that Wordpress cannot access the web. RSS feeds on the dashboard give an error, and the plugins/theme install pages give errors.

 

We've got a Smoothwall box doing our filtering and firewall, so I've added the IP of the VM as a 'location' in smoothwall to bypass the proxy. I've also added the values in the wp-config.php file as shown here: WordPress Proxysupport |

 

Still the same.

 

If I add wordpress.org in SW to the Auth Bypass category, it appears to work, but I'm concerned this may open up users to be able to access some sites we don't want (though most blogs are blocked on wordpress.com not .org I think).

 

Is anybody successfully using the setup above?

[FN-GM]

You could add the Servers IP as a proxy exception. That will allow it straight out with no filtering etc.

[chinesewhispers]

I thought I'd added the IP as a location so that it should bypass the proxy, but it doesn't appear to be doing so.

[FN-GM]

I don't think that would totally by-pass the proxy.

[SteveM555]

Go to:

 

Guardian > Web Filter > Exceptions and add the IP Address of the web server.

On the webserver set the default gateway and DNS as the Smoothwall IP.

 

Should be good to go with that.

[skell]

Add these lines to your wp-config file.

 

define('WP_PROXY_HOST', 'IP');

define('WP_PROXY_PORT', 'PORT');

[chinesewhispers]

Tried all the above with no joy (apart from setting the Smoothwall as the IP for DNS, our AD DNS forwards to SW for DNS anyway). I've added wordpress.org to the auth bypass category for now and it at least allows me to browse plugins and themes.

[Marci]

Re: plugin / theme install...

 

This'll only work if there is incoming access to the web server, and is thus dependant on what ports are forwarded to it on your firewall etc.

For instance, as our web server only has ports 80(http), 443(https) and [random](SSH/SFTP) accessible from outside, it couldn't auto-update / online-install themes & plugins without some tweaking (ala Configure SSH2 Access for Updating WordPress) to enable update via SFTP as all native methods would fail due to lack of ftp/ftps access.

 

Re: RSS feeds

 

These aren't done server-side, they're done client-side via javascript, so your client PCs all need access to wherever the RSS feed is pulled from (*.wordpress.org), not your web server.