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
Can't connect to core #59
Comments
What version of node.js are you using? |
If I'm not mistaken, that should be the latest version. |
As @willrea stated, it's usually due to the node version being too old.
and capture the output to paste it here, perhaps it'll give me a clue on where it stops working. |
It is. I removed the folder anyway and reinstalled but that doesn't seem to fix the issue.
Doesn't look like that will be helpful for you though. 😔 |
quassel/core.log:
Quassel version (Debian wheezy):
|
yup, that's what I was thinking of, your core is too old, you need at least 0.9.x, doesn't know the exact minimum version though, sorry 😕 |
Okay, that's no problem for me. Maybe you should state that in the README or better yet show an error message if that's possible. |
Refer to #60 |
Hey, sorry for reopening that thread. But I work with a dockerized version of quassel-core (v0.14.0) and quassel-web and get the message When I set the IP of the quassel-core as target, I can reach it under the local-IP but when I try thew URL of my qussel web I get It may have something to do with the containers being behind NGINX Proxy Manager, but I am not sure. Can anybody help? |
@JoBilert - I have the same problem as you: https://discourse.linuxserver.io/t/quassel-web-cant-connect-to-quassel-core-ssl-error/7857 I'm starting with LSIO to see if anyone there can help, otherwise I think a new issue should be opened here. I doubt you'll get any help on this issue since it's 8 years old. |
When I enter my login credentials and click on 'Connect', nothing happens. No error, no request and sadly not a chat window.
Server console:
Browser console:
Version:
Browser: Google Chrome version 42.0.2311.152 m
The text was updated successfully, but these errors were encountered: