@Raymond-Bell Thanks, keep us posted.

What is version “Latest trunk” exactly?

@Erek-Beckman Please install the remi repository, or try running:

yum -y update php* --enablerepo=remi,remi-php56

@asbenavides Just a thought, considering the exe is no longer an “MSI” you might want to remove the template and just add the -ms argument to the “Snapin Arguments” section.

Make the Snapin Run With blank
Make the Snapin Run With Argument blank
Change Snapin Arguments to just -ms

@craigcoulson What’s the output of:

mysql -u root

Does it allow you to connect? I’ve seen one other time where, for whatever reason, the root user doesn’t get created when mysql is installed. I’m just guessing that this is a “fresh” install? If it is please run:

sudo apt-get purge mysql mysql-server mysql-client
sudo rm -rf /var/lib/mysql
sudo apt-get install mysql mysql-server

I don’t know all the “packages” and layouts Debian is looking for so it may be slightly simpler, and you may need to adjust the install/erase commands. Essentially all I’m wanting to see:

If you cannot get root access with the mysql -u root remove mysql entirely, re-install it.

I’ve removed the version= string from the fogconfigurationpage testing element as you guys found. Ultimately this version string isn’t needed for anything and should not have been causing any other issues. It would seem, to me, the query string was trying to be accessed as if it were a “direct” page instead of stripping the query part off.

working-1.3.5 has the string updated now.

Please edit the fogserver file /opt/fog/.fogsettings and update the password= field to match what you typed in the management page. After this re-run the fog installer, it will update your system’s fog user passwords.

@palloquin THe simplest method:

Edit the /opt/fog/.fogsettings file and edit between the ''s to set whatever password you want.

Re-run the fog installer.

Well that would make a ton of sense.

A reinstall helped correct the problem with the password.

Can you get us the log? That will tell us a lot more, I hope, than what we’re seeing on this particular snippet of log you’ve given us.

Right now it appears to be saying the exact command it’s trying to run is:

powershell.exe -ExecutionPolicy allsigned -File -ExecutionPolicy allsigned -File -programme "P:\packages\audio video\vlc\inst_vlc.bat"

@palloquin Correct.

Just like you wouldn’t want a website being capable of resetting your windows password on a whim, we don’t allow changing the “users” password from the fog website. Imagine if we did? All you would need to do is type root, password and any person would have access to your system.

@ablohowiak You can remove those two lines and re-run the installer, though I highly doubt it’s going to fix the issue.

But please pull the dev-branch and install. I just pushed an update that released RC 5 and am just building the news page right now. I don’t know if it will fix the issue you’re seeing, but with any luck it just might.

@shoong What’s the error?

Error 500 doesn’t tell us a single thing.

The error 500 (regardless of version installed) will nearly always correlate to a message being thrown in the apache error log.

Please get the last few lines of this file: /var/log/apache2/error.log

@shoong I don’t know where your repository is.

git clone https://github.com/fogproject/fogproject.git
cd fogproject
git checkout dev-branch
cd bin
./installfog.sh -y

@shoong I don’t know. I just know there’s been more work for 1.3.5 than my focusing on 1.3.4.

I’ve already adjusted the refind.conf file to use the “internal” setting that most others were having to change there file for.

The reason “EXIT” was used as the default was at the time this modification was added EXIT was really the only option. Grub types wouldn’t work with EFI, and SANBOOT either. We didn’t have reEFInd back then.

I’m not changing the “default” option. Why? Because that was added quite a LONG time ago. To ‘fix’ it would mean it would only be good for new installs. If I define the exit type for this implicitly, it means those who update will have their configurations changed as well, only really noticeable if they aren’t using rEFInd.

it’s a GUI Update to set either individually on hosts or as the default. I’d more lean on saying put it in the “gotcha’s” under the EFI information on the wiki.

The bottom line, “Could I change it?” Sure I could. “Should I change it?” I don’t think so. Especially now.

@plegrand To install the RC’s yes.

Also, it can be used for “official” releases as well so yes. A single point.