@Scott-B Pleas run find /var -type f -name "*fpm*log*" and post results here. Ahhh, forget about that. Ubuntu has the errors in apache error log as far as I remember. Please take a look at /var/log/apache2/error.log and maybe paste the whole log messages from yesterday and today here.

@DeRo93 said in Database connection unavailable - Login incorrect on FTP and Ubuntu: But maybe you can tell me if this happened because the Ubuntu Server did an Upgrade or something? Probably yes. But you may check the update log in /var/log/apt/history.log…

@stepkinetic You are welcome! Marking this solved…

@Tom-Elliott I wasn’t aware that snapins automatically showed under the groups… If that’s the case then it kinda threw me for a loop. Now to recover from my own little screw up… oh well lesson learned… don’t be a dummy :)

@Tom-Elliott And you can’t calculate all the hours you’ve saved for other admins.

@Tom-Elliott I do believe that is fixed. As far as I have tested anyway. I will report back if anything changes

Updated to ver 6525 before updating the image again. This time around it worked flawlessly as it should.

@Ph3noM Fog doesn’t set a DB password - if fog sets up the DB on a new server, it’s left blank. The installer (at least in FOG 1.3.0 beta) asks you for a DB password just in case you set one in the back end. And of course if that’s the case (and 99% of the time it is) then the field in /opt/fog/.fogsettings would be blank as well.

@Wayne-Workman I did end up figuring it out. It turns out that our data had left over data from a previous export/import. So that’s why not all of our entries in the both tables had corresponding entry’s while some did.

@Polii123 said: @ch3i said: @Polii123 said: But how did they come into my config.class.php file? Maybe a ghost lol F*****g ghots :rage: I think Tom has to code some ghostbusters, so things like that won’t happen again. :joy: 3430 should not allow the brackets at all. I don’t know why it did it to begin with, but worse things have happened I suppose?