This problem is due to the nginx socket files, it seems that nginx does not delete these files before terminating, and in the next run, it gives an error about the existence of these files.
A workaround is to manually remove the socket files before restarting
This problem is due to the nginx socket files, it seems that nginx does not delete these files before terminating, and in the next run, it gives an error about the existence of these files.
A workaround is to manually remove the socket files before restarting