-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
[Bug]: dvl.to cannot be resolved #999
Comments
Looks like the dvl.to domain has expired. I've registered and set DNS on the slightly cheaper dbox.dev, feel free to use it 🙂 (note .dev domains are https only). |
How you make this type of domain ? |
Is this the cause for very slow connectivity to other domains? I'm running Devilbox on a M1-MacBook and feel that as soon as I add the Devilbox DNS looking up other domains becomes very slow. |
Another popular alternative is localtest.me |
dbox.dev doesn't work for me, but localtest.me does. In case anyone is wondering how to use this, you have to change this in the devibox
I then had some issues with some of my domains, so followed the official troubleshooting steps to recreate the containers. I still had some issues so restarted the WSL2 instance, as well as did an empty cache and hard refresh for the domains in the browser. |
Just for more alternatives, I'm using |
Examples in the .env would be good. But the project seems to be abandoned... |
Have you already looked into this bug?
(Optional) Error message
No response
What went wrong?
dvl.to
domain cannot be resolvedExpected behaviour
dvl.to
domain be resolvableHow can we reproduce the bug?
or
https://dnschecker.org/#A/dvl.to
https://mxtoolbox.com/SuperTool.aspx?action=a%3advl.to&run=toolpage
Host Operating System
Linux
Host Platform (amd64, arm64, other)
amd64
(Linux only) Is SELinux enabled?
Yes, SELinux is enabled
Docker version
24
Docker Compose version
2
Devilbox version
3.0.0
Have you removed stopped containers before starting?
Yes
Have you pulled latest Docker images before starting?
Yes
Devilbox start command
docker compose up -d php bind memcd httpd
Config: .env file
Config: docker-compose.override.yml
No response
Config: ./check-config.sh
Log: docker-compose logs
(Optional) Additional information
No response
The text was updated successfully, but these errors were encountered: