Solved. Because Fog’s apache settings are configured in a vhost, the logs are going here on Debian 9:
/var/log/apache2/other_vhosts_access.log

Bild Text

@george1421 said in Location Plugin - enhancement of behavior:

Issues that will need to be addressed is location cidr addresses eclipsing other addresses.

Exactly, I thought about this too. And when there is overlap, as Joe said, we just pick the best match. If there’s a tie, just pick the first one in the tie.

[MOD Note] Forking topic since the issue doesn’t directly relate to this tutorial.

Nearly three weeks without any information.

I’m solving this to keep somewhat clean. If this is still an issue, with proper details, please open a new thread describing it.

@Wayne-Workman unfortunately we will not add this. The ssl directory where your private keys are stored, and should never be accessible via the web GUI. That presents a massive security risk as a single bug in the web GUI could provide anyone with access to your private certs; arguably the most sensitive data on the server.

As the saying goes, security and convience are usually at opposite ends of the spectrum; and this is one thing we will not compromise on.

Exporting your keys as root using ssh is the preferred, and only way, we will support.

Since the feedback has been positive, I’ve cross-linked the old ‘upgrade to trunk’ and ‘getting fog’ articles. I also ask that when people request instructions on getting fog installed, we reference the newer ‘getting fog’ article.

This appears to be resolved now.
I’m going to guess that someone over at Arch Linux botched a build of some package & didn’t know until a day later & fixed it.

@Tom-Elliott When I said I changed from zstd to gzip, I changed it in the image settings via the GUI, pictured below. Then I recaptured & redeployed and it worked fine.
0_1493855732085_zstd and gzip.png

@x23piracy When you run the installer, use the:

-S --force-https Force HTTPS redirect arugments with the installer.

So if you want https support, you would run your installer as:

./installfog.sh -yS

@Wayne-Workman you can make it a hyperlink: e.g. this thread

@Jaymes-Driver said in Debian 8 tutorial:

I am sorry for filling up your thread with these posts,

Nah, it’s fine.

I don’t think Ubuntu is a better fit for a novice really, not for use as a production-server. For end-user desktops & laptops yes absolutely I think Ubuntu is stronger there. But when it comes to fixing / manipulating things in the back-end, when it’s time to open the Terminal, a novice would have equal amounts of challenge whether the OS is Ubuntu or something else.

There’s not really a lot of differences between Ubuntu and Debian, and the differences between Ubuntu & something like CentOS are pretty short.

Off the top of my head… and these lists are missing most of the differences I’m sure but…

Ubuntu:
Security - apparmor & iptables.
update configurations - /etc/apt/sources.list
root login via ssh disabled by default inside /etc/ssh/sshd_config
to update - apt-get -y update;apt-get -y dist-upgrade;apt-get -y autoclean;apt-get -y autoremove
apache is called apache2
OS installer forces you to create a non-root user.
Network configuration is in /etc/network/interfaces

CentOS:
Security - firewalld & SELinux & optionally iptables if that’s your thing.
update configurations - /etc/yum.repos.d/
root login via ssh permitted by default inside /etc/ssh/sshd_config
to update - yum -y update;yum clean all
apache is called httpd
OS installer makes configuring non-root users optional.
Network configuration is in /etc/sysconfig/network-scripts/ifcfg-<interface name>

Similarities:
Both use /etc/ssh/sshd_config
Both use volume groups, logical volumes by default in their respectable installers.
Both have the same apache configuration files, same options available in there.
Both use /var/www/html as their default web root, - only recently.
Both use systemctl - only recently.
Service commands work on both still.
Ubuntu will be adopting firewalld in the future I think.
Both use /home as the user home directory.
Both use /root as the root user’s home directory.
standard linux commands exist on both such as sudo, ssh, mv, cp, rm, ls, crontab, useradd, userdel, realmd, ping, hostname, route, ip, ifconfig, ifdown, ifup, vi, a ton more.

What I’m getting at is - if you know an ounce of Linux - you will be able to work on any distribution without much effort besides some quick google searches to see what it is on this/that. And if you know zero linux you won’t have a easy time no matter the distribution - when it comes time to do work on a server.

End-user non-technical laptop/desktop usage where a person will never open terminal - well this is a different story and Ubuntu would be the best choice here.

is RC30 current working branch? Whooops sorry i missed the RC30 post.

Confirmed, and republished RC-29.

Unexpected referrer check simply wasn’t sending the right class to operate from.

This should now work as intended.

@Wayne-Workman found and confirmed. I was partially aware of there being an issue with this but just kept over thinking how to approach it.

I’ve implemented a solution into working-RC-28 which appears to fix this , among a few others, issue.