Errors 400 on Conversations tab

I was noticing some diferences between the Tiledesk cloud and Community

Cloud

Community

Simply the number of conversations is not loading, neither the agent pics.

And meanwhile, in browser console…

GET http://company.link/dashboard/
[HTTP/1.1 404 Not Found 40ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F609bec896848530012f00bb5%2Fphoto.jpg?alt=media
[HTTP/2 400 Bad Request 140ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F60a7b6fe5e5c250012c5f249%2Fphoto.jpg?alt=media
[HTTP/2 400 Bad Request 140ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F60a7b4db5e5c250012c5efe3%2Fphoto.jpg?alt=media
[HTTP/2 400 Bad Request 140ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F60a56335e9a991001273da2d%2Fphoto.jpg?alt=media
[HTTP/2 400 Bad Request 140ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F60a558b7e9a991001273da29%2Fphoto.jpg?alt=media
[HTTP/2 400 Bad Request 140ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F60a553c2e9a991001273da23%2Fphoto.jpg?alt=media
[HTTP/2 400 Bad Request 140ms]

GET https://firebasestorage.googleapis.com/v0/b//o/profiles%2F60a5526de9a991001273da21%2Fphoto.jpg?alt=media

Can you confirm you are using the last docker-compose.yaml file with updated Docker images?

Yes,I am using the last docker-compose.yaml and I’ve updated the docker images!

@andrealeo , I made these pulls (on github for tiledesk-deployment repository and with docker-compose pull) and since before this I noticed that the url was missing the port number.

And watching the code on tiledesk-dashboard's repository on github last week I notice that at least the ws:// url may be related to WS_URL field on tiledesk-dashboard's enviroment field. I’ve changed the value of this field to the ${EXTERNAL_BASE_URL} but nothing happened.

When I pull the code by docker-compose pull, does docker get the code from github or in docker is another repository?

Can you describe the problem you are having? Please open a separate thread for each issue

Right, actually we have two issues and I’ve mixed the both issues.

I’ll keep this with the Error 400 related to firebase storage, and I’ll create another about the error on calling WebSockets, ok?

ok thanks. if you can please remove from this conversation the other posts