Hi All
I'm frustrated because this is something I have done several times, have working in production and am not able to do again. I suspect there's a piece of understanding I'm missing.
I've installed Apache on a Digital Ocean, Ubuntu droplet:
aptitude install apache2 a2enmod proxy a2enmod proxy_http service apache2 restart
And configured it to forward to port 8938:
nano /etc/apache2/apache2.conf
<VirtualHost *:80> ServerAdmin paul@nakedelement.co.uk ServerName solr.nakedelement.co.uk ServerAlias solr ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPreserveHost on ProxyPass / http://localhost:8983/ ProxyPassReverse / http://localhost:8983/ </VirtualHost>
service apache2 restart
However, when I go to the droplet in the browser I get a 404.
I have an existing droplet which is configured in exactly the same way and when and I access it in a browser via its IP address I get a 404, which is odd, because if I access it via solr.nakedelement.co.uk it works and the url just points to the IP address.
I've tried the obvious thing of removing ServerName and restarting Apache, but there's not change.
What am I not understanding?
On 24 Apr 19:05, Paul Grenyer wrote:
What am I not understanding?
My guess is that you're not using the usual sites-enabled etc method, and that there's still /etc/apache2/sites-enabled/default in there that is getting the requests for the IP addresses.
a2dissite default
May well make your problems go away, though - I'm not sure why you have a problem with having to use the DNS name...
Cheers,
Hi Brett
On 25 April 2015 at 12:48, Brett Parker iDunno@sommitrealweird.co.uk wrote:
On 24 Apr 19:05, Paul Grenyer wrote:
What am I not understanding?
My guess is that you're not using the usual sites-enabled etc method, and that there's still /etc/apache2/sites-enabled/default in there that is getting the requests for the IP addresses.
a2dissite default
May well make your problems go away, though - I'm not sure why you have a problem with having to use the DNS name...
Thanks for this! This command is what I was using in previous configurations. It stopped working on Ubuntu recently and instead of investigating why I, stupidly, started fiddling with other configurations. I've gone back now and googled and the command I actually needed is:
a2dissite 000-default.conf
as the default site name has changed. It's now all up and running and I'm using 'sites-enabled' again.