@Tom-Elliott I figured it out.

I was getting confused by the similar language between the installation process and storage group setup.

A normal installation is just a fog storage node that has a web server and UI on it. A FOG network requires atleast one to work. However a Storage node can be set as the master of a storage group no matter the installation type.

My problem was that because the storage node in the “Bris” storage group did not have a master node setup, the default group could not replicate any images or snapins over. All storage groups must have a master for it to work effectively.

@Tom-Elliott feel free to clarify any of the above rant.

@Tom-Elliott Yes this did work. Thank you for your quick action.

@Clebboii These warnings are safe to ignore. While the REQUEST_METHOD issue you’re seeing has already been fixed in dev-branch, the dashboard page issue you’re seeing is just because sometimes the values are set, sometimes they’re not. Unfortunately there’s no real way to validate cleanly. (at least right away or easily at this point in time. But it’s not causing issues.)

I’m not seeing there being issues with the files syncing? It seems, to me, the location it’s sending the file to (192.168.140.39) isn’t accepting ftp?

Hi @Tom-Elliott,

Currently both nodes are in the same storage group as I want to replicate images and snapins from the Master to the Normal storage Node. I read through some documentation and it seems this should still happen if they are in different storage groups. Is this true?

If so, I believe this second issue should be fixed.

I’m having the exact same behavior.
Was working on the 27, 28 and 29.

Stopped working start of this week (2 september)
Added 3 storage nodes in between.
1a07ba58-be68-4007-a60c-5532e6c42e41-image.png

Greetings.
Same issues here with a LENOVO 50S, realteck chipset.
I’va speed of 9 Gbit/min on capture and 0.6 Gbits/min on deploy.
Debian Fog Server, version 1.5.10.1660, latest and beta kernel : same issue.
Do a bunch of test with an another hard disk, new kernel, same issue.

I tested with 5.15.68 kernel and my download speed go from 0.6 Gib/min to 4.5 Gbib/min !