-
Notifications
You must be signed in to change notification settings - Fork 3
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
Synapse-admin does not work by displaying an error #15
Comments
Same here. |
+1 |
I wonder were we can find the relevant log… |
I think they are already working on a solution for this, but it takes a long time to release it seems. See #13 |
I think this kinda stalled :D - I hope they can fix it soon so we can properly manage synapse. |
It depends on volunteer time and energy, so we will see :) |
Always much appreciation for such volunteer efforts! |
This is still an issue |
Yes same here. I have the latest Synapse and Synapse Admin packages installed..... |
@ericgaspar
|
Doesn't work for me. |
I'm not able to fix via this method either |
Current state of the app should be OK. Please reopen an issue if it arises. |
It's not working for a fresh Synapse admin install and up-to-date Synapse. Admin API has visitors rights. |
Can you share logs from the browser console and the app service? |
Browser console:
Those URLs redirects to SSO if I try to load them. |
On which domain have you installed Synapse Admin? |
I have this in
|
You have ignored my first question and misread my second 😇😅 |
Oh that's right joy In synapse-admin.endpoint.conf:
Synapse is on a different domain. |
I do not understand why it is not working. :/ It works on my server. Here is the directory tree of my NGINX files for Synapse and Synapse Admin, along with their content (port can change depending on the server). Can you check yours match?
|
I have my synapse domain as URL here. I guess you changed yours, as for the rest of these URLs ? The only particular thing I have is that synapse-admin is in a sub.sub.domain. Wait…
This one is very different in my case. I have:
Can I ask you how you generate that folder tree view ? |
I also noticed synapse-admin service was stopped a few days ago 🤔
But can't restart it:
|
If I try to use your nginx conf for synapse-admin, I have a 502 Bad Gateway. No systemd service installed this time (it was from an old backup I guess ?). |
I tried this version #36 |
I think that's an error on my end. I will check that tonight. |
No hurry :) |
I was running an older version of the app (somehow the catalog was not updated on my server...) now it's up-to-date and still working:
Manually. 😅 |
Ok, I have the same, it doesn't work. |
Hum... have you made the user you are logging in with an admin of Synapse? (cf. https://github.com/YunoHost-Apps/synapse_ynh#set-user-as-admin) |
Yes, a long time ago. |
I tried again with both version (normal, v2) with no success. |
Same here. Updated to the latest both synapse and this package. Same error. |
Fixed for me! We realized that in the file |
Doesn't work for me, I can't connect (it seems to work and then "the session ended"). |
This is what I have in that file:
|
I have a similar one 🤔 |
Make sure you also did this change in nginx https://github.com/YunoHost-Apps/synapse_ynh/pull/392/files My nginx is this:
|
Done, no change :( |
Did you restart Nginx and also the Matrix service? Maybe reboot you server. |
Oh no, just Nginx. I'll try. |
Damn....but do you get the same exact error as before? |
No. |
Ok so perhaps this is another issue than the one in the OP. |
Does anyone knows how to get some log to diagnose this ? The only thing I found was in the web console : |
The application has not been working for several weeks
Hello, I tried to use the application a month ago, and it displayed the message next error message :
I left it out hoping that it was going to be updated and the problem fixed, but unfortunately it presents still the same malfunction, with this error that is constantly displayed at launch.
Thank you for helping me to solve the problem.
The text was updated successfully, but these errors were encountered: