-
Notifications
You must be signed in to change notification settings - Fork 179
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
cannot set headers after they are sent? #22
Comments
rolled back to node 16.18 and that fixed this for now. interesting |
Are you 100% sure the explorer is working fine after rolling back to node 16.18? Typically the "Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client" msg means you aren't able to connect to your wallet because of wrong or blocked port, wallet not runnig, etc. I installed and tested node 18.12.1 and see no problems on my end, so either you do have wallet connection issues, or else maybe it is a specific version of one of the dependencies that had problems with newer node versions. You can upgrade your dependencies by running |
Yes it is no longer throwing that error. It was before I even set the crib
jobs up so the wallet is never instigated. There are a lot off issues with
the npm packages 7 major 2minor vulnerability’s when using —only=prod I
will try install a second one using node 18+ Fresh and install how you
describe and also how my friend has done it but he’s on Ubuntu 18 I’m on
20.4 not that that should be anything except npm differences with pack
versions
|
i am getting this as an error every time someone connects. or the page refreshes. any help apreciated
The text was updated successfully, but these errors were encountered: