@dafyre said in Network routing question:
@dafyre said in Network routing question:
DNS server is at 10.50.235.235
Configure your computer to look to 235.235 for DNS... and configure the DNS server at 235.235 to forward anything it doesn't recognize along to your Meraki?
I added 235.235 as an additional DNS in the 250.254 network.
I tried this yesterday but silly me forgot to "refresh" the NIC so it could grab the new settings.
All is good & working.

Vultr support was interested after my previous response.
"We understand your concerns and appreciate you bringing issues to our attention, however, we are not seeing this issue with our Fedora 30 build when running updates. It is possible that something is different when upgrading the distribution manually and this is not something we would be able to troubleshoot as we are not seeing the issue.
Does the OS itself throw an error when attempting the update? If there is an error being throw by the OS we can try to assist in figuring out what it means and try to point you in the right direction, but as a self-managed service our in depth troubleshooting steps for software issues is extremely limited.
Thank you for your understanding."
I provided them with specifics on how to produce the error.

@matteo-nunziati said in Fedora 30 Workstation default partition scheme:
@black3dynamite cool... If not official docs what else? Strange...
It is the official docs. I'm just being stubborn about some screenshots that doesn't go with the current release.

Dont' use bullet/number lists in instructions and guides like this. it makes it annoying for those that want to copy and paste.
This guide is assuming that you are running as root. If not prepend everything here with sudo.
Install the salt-master package
dnf install salt-master
Open the required ports in the firewall
firewall-cmd --add-port=4505-4506/tcp --permanent
firewall-cmd --reload
Enable the salt-master service to start on boow, and also start it now.
systemctl enable --now salt-master.service

@Dashrender said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update:
@scottalanmiller said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update:
@Obsolesce said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update:
Wow so they just decide to up and change ports? And I thought Windows updates were bad...
They accidentally hard coded to the default.
did you report it?
Unlikely.

@scottalanmiller said in Updating to Fedora 30 Gives Pix Error:
Doing an upgrade from Fedora 29 to Fedora 30 and you get...
Error:
Problem: package pix-1.8.2-1.fc29.x86_64 requires libexiv2.so.26()(64bit), but none of the providers can be installed
- exiv2-libs-0.26-12.fc29.x86_64 does not belong to a distupgrade repository
- problem with installed package pix-1.8.2-1.fc29.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
This seems to happen with most normal workstation installs of Fedora. Easiest thing to do is simply remove Pix.
sudo dnf remove pix -y
Your update should work fine after that.
I don't ever use it. But, yeah it is there by default.