Linux

When mega-sync fails with the following message: Failed to sync folder: Invalid argument. Unable to retrieve the ID of current device the problem is often not the sync path itself. In my case, the real issue was that the Ubuntu environment deployed inside Docker did not have a valid machine ID. Why This Happens MEGA relies on the current device ID when creating or managing sync relationships. On some minimal Ubuntu container images, /etc/machine-id can be missing or empty. When that happens, mega-sync cannot identify the current device correctly and returns the misleading Invalid argument error. ...

If you use systemctl status nginx to check nginx status you may find a pid error appear on status panel. The words that appear may be : Can't open PID file /run/nginx.pid (yet?) after start: Operation not permitted Or Can't open PID file /var/run/nginx.pid (yet?) after start: No such file or directory This is becasue the pid file not generate before the nginx booted. The solution is to add following sentence into /usr/lib/systemd/system/nginx.service, it will let nginx wait 0.1s before executing the executable. ...