My next article will be on load-balancing FOG’s web frontend and database backend… I’ve just not wrote it yet… Don’t wait on me, it might be a while.

Set the username manually in the database? That’s what I’d think about doing for this very rare one-off. I can help you try that.

it seems generating passwords in fog has been an issue for a while… be it special characters that need handled or double vs single quotes to contain it…

Lately in my own projects, I opt for very long passwords made from upper & lower case letters and numbers randomly. I’m talking 32, or 64 characters long. Typically I look up the maximum length supported password, and generate one of that length, just letters and numbers.

@martial A temporary solution would be to manually reset the encryption. Steps on this are in the wiki here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Reset_encryption_data
That’s just to get you moving along. Please still help us figure out why the button is not appearing for you.

You might also consider cleaning your database…
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands
You can replace the DELETE with SELECT * to see the entries, instead of deleting them.

Have you tried ssh aliases?

For example, if you are root and set the file /root/.ssh/config as such:

Host fog-server
    User root
    HostName 10.0.0.28
    Port 22

You can then just type ssh fog-server and bam, you’re in.
Makes scripting a bit simpler… Particularly makes getting around in your systems faster while in the shell.

Agreeing with @Sebastian-Roth though. If ssh works manually, but doesn’t in cron, it’s maybe a user issue. You can figure out who it’s executing as like such:
whoami > /tmp/whoami.txt 2>&1
Put that towards the top of your script, see what it says.

@TBuzaTechnician said in Auto-Installing FOG with HTTPS enabled issues:

but I have a habit of using sudo anyway.

This has in-fact caused many people problems. I don’t know why, don’t really care why, but using sudo with the installer doesn’t work. As Sebastion said, properly log in as root with sudo -i and then execute the installer.

@sudburr Are you aware of this article? https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@astrugatch The link is in my signature. Testing is suspended by request of @Sebastian-Roth until the 20th of this month. The last test results can be seen on the site.

My memory is very foggy on this (pun intended), but I think the Max Clients setting inside of each storage node is what determines how many snapins can run at once.

@TBuzaTechnician You can also pre-place your .fogsettings file, rather than modifying the source code every time. Here’s a writeup on that settings file:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings
Modifying the source is cool too, whatever shakes your feathers.