-
Notifications
You must be signed in to change notification settings - Fork 69
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
DNS Issue #75
Comments
I'm using Deck v4 on Mac 12.5.1 |
Hi @eriku We tested multiple stacks with DECK v4 on MAC 12.5.1 but couldn't reproduce the issue. Can you please give us some more details about what type of issues are you facing and also the Stack Logs if possible. Some screenshots along with the info will help immensely. Thanks |
I'm not sure how to troubleshoot the issue. There doesn't seem to be anything that is standing out to me as to why the *.stacks.run all of sudden stopped working. How does DECK redirect that domain to my localhost? I've looked at my hosts file and didn't see any entry there. I've attached a screenshot of the DECK window as well as added all of the Terminal Output and Apache Log. Thank you, ----------- TERMINAL OUTPUT ----------
---------- APACHE LOG ----------
|
Hi @eriku Can you please send us the output of this following command by running it in your local terminal - sudo lsof -PiTCP -sTCP:LISTEN We have tried many different steps to replicate this issue on our side without any success. This may help us to get a step forward in fixing your problem. Thanks |
Hi, i had the same problem. For me, it was because I was running Laravel Valet on my Mac, and I guess this was listening on https. After removing Laravel Valet, everything works perfect. |
Hi, @w00p ,thanks for reporting. Appreciate your feedback here. |
I am using DECK 4.2.0 on Mac 12.6 and I have the same problem with HTTPS, all the requests for css, js and ico fail. |
Hi @wblondel , Can you please send us the output of this following command by running it in your local terminal - |
Hi @nabad600 , sorry for the late reply. |
Hi @wblondel |
None of my stacks are working when using the pretty domain .stacks.run, only 127.0.0.1:****
The text was updated successfully, but these errors were encountered: