-
Notifications
You must be signed in to change notification settings - Fork 71
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
ECONNREFUSED error #147
Comments
Seems it was being caused by an outdated version of DECK! |
Hi, @callumb |
Hello! What logs do you need? I had to restart and it's now broken again! Getting 502 Bad Gateway on ALL my sites that run though Deck. This only happens on the secure domains (*.stacks.run) and not the direct IP. Looks to be an issue with nginx where ever that is being run rather than my sites as they all use Apache. I love this app but these issues are killing it. |
Hi @callumb , please use direct IP access as a temporary solution. We have to replicate the issue on our side to be able to fix this. A proxy server runs in the background, which serves the HTTPS links, so it has something to do with that. Can you please share the configuration of your system? Either here or send an email at [email protected] |
Hi, Thanks for getting back to me with this. What kind of information are you looking for? OS Version, Stacks used etc? Currently running MacOS 13.4 on an 2018 Intel, latest version of Deck. Let me know where the Deck logs are located and I will email them over. |
And now I can't access the non secure as browsers now force SSL it seems! I really need some replies to this! |
Hi @callumb , SSL already update please close you app and relunch it's work. |
I have this issue with a new LAMP stack in where I go to the site and it will what feels a 50:50 chance of getting just ECONNREFUSED or the page expected. Chromes console log says: 502 (Bad Gateway) and no other errors I can find. It's the same for both non SSL and SSL urls.
The text was updated successfully, but these errors were encountered: