IPV6 support?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
When enabled ./bin/start the server binds to 0.0.0.0:port. However if I've configured [::]:port, the ipv6 port is not binded and can't be accessed.
When I changed to the on /lib/docker-compose-base.yml
- "7880:80"
- "[::]:7880:80"
The server listens on IPV6 and can be connected, but when actually in the project the editor couldn't load "Sorry, something went wrong"
Steps to Reproduce
Expected Behaviour
Observed Behaviour
Context
Technical Info
- URL:
- Browser Name and version:
- Operating System and version (desktop or mobile):
- Signed in as:
- Project and/or file:
Analysis
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ./bin/start and the port mappings in lib/docker-compose-base.yml, then reproduce the IPv6 configuration described in the issue. Check why the server is not reachable on the configured IPv6 port and why the editor fails to load afterward. Done means the server accepts IPv6 connections and the editor loads normally through that setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100