-
Notifications
You must be signed in to change notification settings - Fork 282
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
Seafile client is connecting to wrong server #1
Comments
Hi, Seafile will remember old IP. Two ways to solve it:
|
Thanks. I did the first and "resyncing" again worked. |
ghost
mentioned this issue
Oct 21, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
We had seafile in our local server first and used a local ip to connect. No problems.
Then we gave it another ip so some people that were outside of the local network could connect. No problems.
After that, there was another change of ip, because they connected it to a different switch. The ip changed again.
I login in the new ip seafile (port 8000) with success, I create a new folder. I try to download it and it keeps contacting server without success.
I saw the ccnet log and I see that it's trying to access the old ip (2nd one in this story) instead of the new one. (when downloading a NEW folder created in the last ip seafile)
I uninstalled and installed it again and keeps with the same problem. How can I change this? My colleagues didn't have the same problem.
I can connect to the seacloud server without problems.
Regards,
The text was updated successfully, but these errors were encountered: