Skip to content
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

Issues when ipv6 is disabled #133

Open
EricSesterhennX41 opened this issue Jun 9, 2020 · 5 comments
Open

Issues when ipv6 is disabled #133

EricSesterhennX41 opened this issue Jun 9, 2020 · 5 comments

Comments

@EricSesterhennX41
Copy link

hi, i get the following error when i have ipv6 disabled via

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

[CRITICAL] An exception occurred during server startup: Failed to start server '[::1]:37358': [Errno 99] Cannot assign requested address

I assume this error condition should be added?

isinstance(e, socket.gaierror) and (

@tasn
Copy link
Member

tasn commented Jun 9, 2020

Grrrrrrr... :|
As a workaround, you can just set the ETESYNC_SERVER_HOSTS environment variable to "127.0.0.1:37358". I'll take a look at how to resolve this.

Does it actually prevent etesync-dav from working on ipv4 too, or is it just an error message?

Thanks for reporting.

@EricSesterhennX41
Copy link
Author

It stops the server at this point, so no working ipv4 in this case. As a workaround I enabled ipv6 on the loopback interface.

@tasn
Copy link
Member

tasn commented Jun 9, 2020

Thanks for the info. If I may ask, why are you disabling ipv6 in the first place?

@EricSesterhennX41
Copy link
Author

I currently have no actual use for it, so i avoid it.

@tasn
Copy link
Member

tasn commented Jun 9, 2020

Fair enough. Thanks for the info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants