-
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
Errors from MarshalJSON *signaling.AsyncMessage: unexpected end of JSON input #642
Comments
same error (( |
I had the same issue. when you build there are two files in bin proxy and signaling. I simply changed the ownership for both to the user (the one which is configured in systemd for the service), and it worked. |
Same issue, changed ownership of proxy and signaling files, upgrade go, resinstall all from scratch on another server : nothing change .. Don't understand what I'm doing wrong .. Even with all my firewall rules bypassed or with allow = all option, I have every time the same error. And the json given seems to have a correct format (in logs, don't when it's "unmarshalled") .. PHP : 8.2 Until the 28.0.2 Nextcloud version all was ok but with oldest signaling, nats, janus and usrsctp version and with another high backend server that have the old version, all is ok (without sip dial-out protocol cause it's unsupported with it). |
Please check if the solution from #180 (run |
I am using following |
Oh ok !! So sorry, I did not find this issue :/ sorry for the disturb and thanks a lot ! :) |
Ok, closing then. |
I set up the high performance backend. But I always get errors from MarshalJSON.
Does anyone have any idea where this error is coming from?
The text was updated successfully, but these errors were encountered: