-
-
Notifications
You must be signed in to change notification settings - Fork 570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch server #1075
Comments
Related to #709 |
Deleting and recreating services and projects, then deleting the server and recreating it doesn't work either. I'm now trying to reset the new server in case the problem comes from it. |
I don't think this is a bug A simple solution, is basically update the IP in edit server, and enter the ssh key again, only that of course you would have to deploy each service, re-save the domains created, volumes, why? because if you change the ip you are pointing to a new server so you would have to re-deploy and save manually in each section as in domains and volumes to sync all to the new server |
Regarding the error you have, it's basically that you don't have root permissions, you explicitly need to use the root user to prevent permissions problems with docker. |
To Reproduce
Current vs. Expected behavior
Editing the current server fails. I had to copy the setup script and run it on the machine by SSH.
Two steps are still failing. I cannot deploy any service, I'm getting this error : "permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/containers/select-a-container/json": dial unix /var/run/docker.sock: connect: permission denied"
Provide environment information
Which area(s) are affected? (Select all that apply)
Installation
Are you deploying the applications where Dokploy is installed or on a remote server?
Remote server
Additional context
No response
Will you send a PR to fix it?
No
The text was updated successfully, but these errors were encountered: