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

invalid docker-compose file with ipv6 #256

Closed
hanneshier opened this issue Mar 19, 2021 · 4 comments
Closed

invalid docker-compose file with ipv6 #256

hanneshier opened this issue Mar 19, 2021 · 4 comments
Labels

Comments

@hanneshier
Copy link

Error description:

I just used the fresh-start.sh script setup nginx, but i get an error message all the time. I used the --activate-ipv6 flag

Steps to reproduce

Install the container following the readme.md procedure.
Start the setup with bin/fresh-start.sh --activate-ipv6

Expected result

Working nginx-reverse-proxy

Error result

ERROR: The Compose file '/home/hannes/proxy/bin/../docker-compose.yml' is invalid because:
services.proxy-web-auto.ports is invalid: Invalid port "::/0:443:443", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]
services.proxy-web-auto.ports is invalid: Invalid port "::/0:80:80", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]
>>> Success!
[end]-----------------------------------------------------------------

[ERROR]---------------------------------------------------------------
There was an error starting the service at '/home/hannes/proxy/bin/../'
----------------------------------------------------------------------

Comments

@hanneshier hanneshier changed the title invalid docker-compose file invalid docker-compose file with ipv6 Mar 19, 2021
@evertramos evertramos added the bug label Mar 19, 2021
@evertramos
Copy link
Owner

evertramos commented Mar 19, 2021

There is a bug in the script, I will fix today, but please try to set your IPv6 address in the compose file manually and try again.

@hanneshier
Copy link
Author

Thank you! Its working now

evertramos added a commit that referenced this issue Mar 19, 2021
@evertramos
Copy link
Owner

Ok!

Issue fixed. You can try again from scratch it should work now. Let me know if you have any other issues.

@hanneshier
Copy link
Author

I restarted the script from scratch and everything is working as it should. Thank very much for the quick fix!

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

No branches or pull requests

2 participants