Virtualmin & Varnish: problems using non-standard Apache port

18 posts / 0 new
Last post
#1 Wed, 12/14/2011 - 04:50
John_B

Virtualmin & Varnish: problems using non-standard Apache port

Just evaluating / getting used to Virtualmin. Using Apache on non-standard port (in my case to use Varnish), this thread is relevant https://www.virtualmin.com/node/19887

There are problems: 1. When Virtual host is configured for non-standard port, Server Configuration > Website Options returns the error "Website options cannot be edited, as no Apache virtual host for mysite.com port 80 was found!" 2. Every virtual host must be individually edited to change port. Since apache is no longer listening on 80, it would useful for this to be automated. It would also be useful to be able to change other settings globally e.g. change php handler, and override / bulk write the local php.ini.

Wed, 12/14/2011 - 07:46
andreychek

Howdy,

Since folks are looking to use port 80 for alternate web servers (be it Nginx or Varnish), it might be good to get Virtualmin to support that configuration a bit better so you aren't manually editing things. I'll talk to Jamie about that.

As far as globally changing the php.ini file -- that's something that can be done via the Virtualmin command line tools. You can run this command to see the options:

virtualmin modify-php-ini

Wed, 12/14/2011 - 08:04
skopy

mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....

Wed, 12/14/2011 - 08:21
John_B

You need a 64 bit OS. You can do apt-get install varnish, I do apt-get install varnish-2.1 as I had problems with Varnish 3. Getting an older version is trickier on Centos with yum but possible. Then you configure it in /etc/default/varnish, (/etc/sysconfig/varnish on centos). I use option 2 in that file as I use Drupal and use the vcl provided for Pressflow 6.22.

You set Apache to listen on the backend port set in your configuration (a *.vcl file if you use option 2 in /etc/default/varnish). Often people use 8081 or 8080 for Apache to listen. With virtualmin you might need to change /etc/apache2/ports.conf

Start Varnish on port 80. Can be done from command line but just as simple to set the various flags in the configuration files. NB getting Varnish to listen on 80 needs to be set manually, the port on which Varnish listens with default config is for testing. Now your can view your website (assuming you have set Virtualmin's virtual host for the site to mysite.com:8081) direct with mysite.com:8081 and via Varnish with mysite.com

Now you need to worry about getting the correct VCL settings for the type of website and version of Varnish.

Tue, 04/16/2013 - 17:32
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:32
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:32
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:32
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:32
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Tue, 04/16/2013 - 17:33
alanf

I know it is an old thred but, did you get it working?

'mind sharing how you installed varnish?

i always end up with default site loading...

pulling my hair out....'

Varnish is installed fine as per @John_b, but all teh named virtual servers go to the site. There must b e asimple trick in teh config that I'm missing, but pulling what is left of my hair out.

Wed, 04/17/2013 - 03:37
alanf

..... sorry ... but the 'save' button appeared not to work ... but evidently it does

Tue, 05/07/2013 - 16:38
John_B

I did not see your post till now. Probably you got it working. First thing is to put Apache on a non-standard port and check your sites are all still working (e.g. if Apache is on port 8080 check sites at e.g. www.example.com:8080). Then get Varnish listening on port 80 and connecting to Apache on 8080 or whichever port it is listening on.