How to set up a working Apache VCL service?
How to set up a working Apache VCL service?
Log In to Comment
1 Answer
This guide from the Apache VCL official documentation will walk you through setting up VCL.
I do not know the details of what you’re planning on setting up but I should warn you that running software in a nested virtualization environment (a VM running inside another VM such as running VMWare/Virtualbox on a droplet) while it may work, will almost always have extremely poor performance.
Have another answer? Share your knowledge.
Related
-
question
.htaccess and symbolic links?
So I am currently using a particular app on apache that is hosted on its own subdomain. In the root directory of this app there is an .htaccess file with the following code ``` RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_URI} !(.*)/$ RewriteRule ^(.*)$ /$1/ [L,R=302] RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ /index.php/$1 [L] ``` I want to create a symbolic link in the directory to link to a completely different app so requests to subdomain.domain.tld/symboliclink/ would use the symbolic link created in the root directory of the subdomain app. The only problem is the .htaccess file above redirects all requests back to itself. How can I set up the subdirectory symbolic link to ignore this .htaccess file so requests to the symbolic link from the web will correctly route traffic while keeping the .htaccess file above unmodified?
-
question
After LAMP stack tutorials, I can't find my site on localhost
I'm a student trying to figure out how to get LAMP stack working on my laptop for Ubuntu 18.04. I need it for a project I'm working on at school and out of school. I followed a few tutorials, first https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-ubuntu-18-04 second https://www.digitalocean.com/community/tutorials/how-to-install-the-apache-web-server-on-ubuntu-18-04 third https://www.digitalocean.com/community/tutorials/how-to-install-mysql-on-ubuntu-18-04 fourth https://www.digitalocean.com/community/tutorials/how-to-install-and-secure-phpmyadmin-on-ubuntu-18-04 to make a long story short, I set my domain as abc and this is me looking at it in terminal Skynet:/var/www/abc$ ls index.html websitedirectory index.html is from the second tutorial and displays: "Success! The your_domain virtual host is working!" The index.html works fine and displays when I go to url localhost in firefox. If I try to do localhost/websitedirectory I get a blank page and if I try to do www.abc/websitedirectory/login.php (I added login.php into /etc/apache2/mods-enabled/dir.conf to prioritize it) I also get a blank page. I'm not really sure what I'm doing wrong and how I can get my actual site to display using the LAMP stack. I was using the lampp package from apachefriends.org and I had my site working with that, but I'm trying to figure out how to use it with LAMP stack instead and to apply it to real world situations. Would anyone be able to clarify this for me and explain what I'm doing wrong. Thank you in advance. Big thank you to the tutorial authors: Justin Ellingwood, Kathleen Juell, and Mark Drake
-
question
I'm getting a weird error while installing PIwik
ERROR MESSAGE: GET request to piwik.php failed. Try whitelisting this URL from HTTP Authentication and disable mod_security (you may have to ask your webhost). For more information about the error, check your web server error log file. After making this change, restart your web server. *** But I don't have mod_security enabled. (I checked via ```sudo a2enmod mod-security```) I can't make sense of it. I installed Piwik easily enough on a cheap shared host, but I'm getting this inexplicable error message on my DO server. Any suggestions?
-
question
How do I permanently redirect www.subdomain to subdomain when using Wildcard SSL
I've setup a staging server for client viewing using a URL structure of subdomain.domain.tld (e.g.: client-abc.my-staging-site.com, client-xyz.my-staging-site.com, or whatever.my-staging-site.com). * subdomain = "client site name" * domain.tld = "my staging domain with top-level-domain." Please note that I've already installed a Wildcard SSL. Thus far, I can get www, none-www, and none-ssl (i.e., http) to redirect to none-www with ssl (i.e., https) within my apache vhost file (see below). I.E., I have the following URLs redirecting successfully to https://subdomain.domain.tld/… * http://www.subdomain.domain.tld/ * http://subdomain.domain.tld/ Which is accomplished via this apache vhost file, subdomain.domain.tld.conf: ``` <VirtualHost *:80> # vhost domain with www in front of subdomain ServerName www.subdomain.domain.tld # permanent redirect www to none-www and http to https # must have a second <VirtualHost *:80> set up # change https to http if there is no SSL certificate # this is faster than .htaccess; Redirect permanent / https://subdomain.domain.tld/ </VirtualHost> <VirtualHost *:80> # vhost domain without www in front of subdomain ServerName subdomain.domain.tld # rewrite rules enabled RewriteEngine On # redirect http to https # comment out if there is no SSL certificate RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [QSA,R=301,L] #…all other normal config stuff goes here… </VirtualHost> <IfModule mod_ssl.c> <VirtualHost *:443> # vhost domain ServerName subdomain.domain.tld #…all other normal config stuff goes here; including ssl stuff… </VirtualHost> </IfModule> ``` However I <^>can not<^> get the following to redirect to https://subdomain.domain.tld/… * https://www.subdomain.domain.tld/ I've tried using rewrite rules in both the vhost conf file and .htaccess file, e.g.,… ``` # rewrite rules RewriteEngine On # remove the www on sub-domains; however because the ssl is called before the rewrite rules # the browser will complain; if using a wildcard ssl, only the first sub-domain level # is supported the workaround could be to add every virtual host name in the Subject Alternative # Name (SAN) extension, the major problem being that the certificate will need to be reissued # whenever a new virtual server is added; nonetheless, if the end-user accepts the security # risk and proceeds, the url will be rewriting to the none-www which is secure RewriteCond %{HTTP_HOST} ^(?:www\.)?(.*)$ [NC] RewriteRule ^(.*)$ https://%1%{REQUEST_URI} [QSA,R=301,L] ``` Please also note, for some reason, when accepting the browser warning for security risk the browser retains the URL of https://www.subdomain.domain.tld/ (<^>not good<^>) and displays the files from the very first vhost on the server (<^>also not good<^>). If I can't redirect, at least help me figure out how to disable this odd result. Any suggestions would be welcome. Thanks in advance.