@george1421 Thanks for your advice! I will consider building a more distributed FOG environment once more clients will be setup with FOG.

Btw should I mark the thread as resolved or something?

Hey all!

I think the title is pretty self-explanatory on what I am trying to achieve. I am deploying linux machines with fog and want to set the hostname to something like my-company-pc-5.
Unfortunately, the UI only allows me to enter 15 characters. Is there a way to disable this limitation?

Many thanks,
Tom

So I followed @george1421 advice and removed the public IP from my FOG instance. Instead I connected all nodes via the zerotier network.

Clients can still be setup without joining them to the zerotier network by using a router which is configured to connect to the same zerotier network (“site-to-site” in a wider sense).

Thanks @george1421 for your reply, I will reconsider my setup and try to make the master node not public. Can you imagine any immediate problems if only the storage node could reach the master node and the clients can only contact the storage nodes?

Btw I fixed the original problem by properly setting the IP of the master storage node to it’s public IP instead of the private one.

Dear all,

I am fairly new to this project and I am currently trying to set up my own system of a master and storage node. Unfortunately, the moment I create a capturing task the client is not able to boot from my storage node anymore (HTTP 5xx error appears in the second stage). When I delete the task from the main server again the booting succeeds and the iPXE boot menu is displayed.

About the setup:

The master node is running somewhere in the cloud and can be reached via a public IP address, while the storage node runs locally in my network without a globally routable IP (local only).
My idea to resolve the problem of replication was to connect the two systems via a shared network such as zerotier. This works so far that the master detects the storage node and all its information.

I already tried to add two storage nodes to the master server, one with the IP of the zerotier network and one with the local IP in the hope of fixing something without any luck.

I know that this is not necessarily a default scenario, but I did not find another way of saying a FOG server in the cloud with a local storage instance while using the FOGImageReplicator service.
Any pointers, ideas or other help is well appreciated! Thanks!

Master Node:
Internal IP: 10.172.0.14
Public IP: 36.xx.xx.xx (resolved by fog-cloud.myserver.com)
Zerotier: 10.147.25.116

Storage Node:
Internal IP: 192.168.1.194
Zerotier: 10.147.25.117

Details:
Installation method: git
FOG version: working-1.6
OS: Ubuntu 18.04 LTS
HTTPS: yes
Custom CA: no

Storage node config:

You will need this, write this down!
IP Address:          192.168.1.194
Interface:           enp0s3
Management Username: fogproject
Management Password: *************************

From the apache error log from the storage node:

[Wed Jan 20 23:44:19.091107 2021] [proxy_fcgi:error] [pid 8722] [client 192.168.1.114:20538] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Exception: No master nodes available in /var/www/fog/lib/fog/storagegroup.class.php:283\nStack trace:\n#0 /var/www/fog/lib/fog/bootmenu.class.php(1384): StorageGroup->getMasterStorageNode()\n#1 /var/www/fog/lib/fog/bootmenu.class.php(419): BootMenu->getTasking()\n#2 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#3 {main}\n  thrown in /var/www/fog/lib/fog/storagegroup.class.php on line 283\n'

In case it helps… this is the generated boot.php file from the storage node.
boot.php.txt