-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 complete admin using the API #1846
Comments
Using
You can access the Synapse Admin API on the Client-Server API port, at Alternatively, you can access it on the container network (named |
So accessing the api via this method: You can access the Synapse Admin API on the Client-Server API port, at https://matrix.DOMAIN. I have to expose the api with: matrix_nginx_proxy_proxy_matrix_client_api_forwarded_location_synapse_admin_api_enabled: true in the vars.yml file before running the playbook? |
Hi @spantaleev sorry for hijacking this issue. I am here to improve I'd kindly ask if you could take a minute and confirm that this information is entirely correct :-) Thanks a ton in advance! One question berforehand: In that sentence, do I understand correctly that the hostname
|
I think we need If you access them from within the container network (using From what I see, there are 2 options for using
Actually, containers started on the same network (
Yes. We create a custom Docker bridge network ( As with all other things, the network name is configurable via the |
Thanks for this superdetailed answer @spantaleev. All clear to me now! will adapt the readme and probably even additionally point here directly. Why not. And thanks for the heads up. It is about time to provide synadm as a container ;-) |
The Thanks again @spantaleev for your help! Appreciated! And BTW thanks for maintaining matrix-docker-ansible-deploy! Great project helping admins to spread Matrix :-) |
Playbook Configuration:
My
vars.yml
file looks like this:Matrix Server:
Ansible:
Working fine
Problem description:
Installed the server via the playbook. All good. I need to get the admin api working but its not. Tried the following commands with ' & " in various locations:
sudo curl -H "Authorization: Bearer syt_***************" http://localhost:8008/_synapse/admin/v1/room/\!LXxm**********sHphYK:**************.com/media
sudo curl -H "Authorization: Bearer syt_***************" http://localhost:8448/_synapse/admin/v1/room/\!LXxm**********sHphYK:**************.com/media
sudo docker exec matrix-synapse curl -H "Authorization: Bearer syt_***************" http://localhost:8008/_synapse/admin/v1/room/\!LXxm**********sHphYK:**************.com/media
sudo docker exec matrix-synapse curl -H "Authorization: Bearer syt_***************" http://localhost:8448/_synapse/admin/v1/room/\!LXxm**********sHphYK:**************.com/media
sudo docker exec matrix-synapse curl -H "Authorization: Bearer syt_***************" http://mydominname.com:8448/_synapse/admin/v1/room/\!LXxm**********sHphYK:**************.com/media
Do i need to call api from inside the container?
Do i need to use iptables to route from 127.0.0.11 to the backend DNS resolver in the Docker Engine?
I even tied installing synadm. Same issue
Can someone give me an example of an api command.. im not sure if im using the correct commands and there are no real word examples in the doc.
Client (please complete the following information):
Additional context
Getting the following errors (out of synadm) and nothing out of the server with the api:
reply: 'HTTP/1.1 400 Bad Request\r\n'
header: Server: nginx
header: Date: Sat, 21 May 2022 03:14:40 GMT
header: Content-Type: text/html
header: Content-Length: 248
header: Connection: close
WARNING Synapse returned status code 400
ERROR JSONDecodeError while querying Synapse: Expecting value: line 1 column 1 (char 0)
Media list could not be fetched.
These are the ports i have open:
netstat -tnlp
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:3478 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8448 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:5349 0.0.0.0:* LISTEN -
tcp6 0 0 :::80 :::* LISTEN -
tcp6 0 0 :::3478 :::* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::443 :::* LISTEN -
tcp6 0 0 :::8448 :::* LISTEN -
tcp6 0 0 :::5349 :::* LISTEN -
The text was updated successfully, but these errors were encountered: