Topics created by Wayne Workman

I made the changes and did a test run, dev-branch completely passed.

@Wayne-Workman Probably one of the configs were changed and the updater is asking what to do. The best I could find quickly is: https://serverfault.com/questions/259226/automatically-keep-current-version-of-config-files-when-apt-get-install/593640 Try: apt-get update;DEBIAN_FRONTEND=noninteractive apt-get dist-upgrade -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" --force-yes What a monster of a command…

Thanks to Wayne I had access to the RHEL 7 machine for a quick test and seems like we hit it with the latest fix. Installer went through like a charm. So RHEL is back in the race I suppose.

@Wayne-Workman Ahhh, now I see. Looking at the certificate on the website I see that there was a new one issued not long ago. Certificate date begins at 08.05.2018! Just wondering why I don’t run into the same issue. Maybe your git is keeping some kind of certificate cache?

Removed. Well, kept the surface-pro-4 matching element, but just removed the 7156 portion.

@Wayne-Workman thanks for reporting, the issue has been fixed. It was caused by the anti-spam plugin being stale.

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

@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.