Bug: failed to operate with openim-admin-front
Sylariam opened this issue · 8 comments
What happened?
[Background]: I have successfully installed im-server and im-chat, and verified using the official Android app. It works perfectly. Based on my k8s cluster configuration, I did made some modifications, like using Aliyun LB instead of Nginx Ingress.
[Issue]: While exploring openim-admin-front, I encounter a CORS error:
It seems that the requests from the admin-front are not correctly requesting my cluster service(the request url looks like your official website. is this a default value?). I attempted to search through the source code but found nothing. Could you help me identify this problem?
What did you expect to happen?
login and use the admin functionalities
How can we reproduce it (as minimally and precisely as possible)?
access {host}/openim-admin-front/login
Anything else we need to know?
No response
version
Cloud provider
OS version
Install tools
I apologize for any inconvenience caused by the issue regarding the URL prefix in the openim management backend. It seems that we have overlooked the routing for nginx. Rest assured, our team is actively working on resolving this matter. Please allow us some time to rectify the situation. Thank you for bringing this to our attention and for your patience.
The mirror has been updated. Could you please try clearing the local registry.cn-hangzhou.aliyuncs.com/openimsdk/openim-admin-front:latest and then try again? Thank you for your cooperation.
Have you had a chance to update the code and delete any local images? It's an important step in ensuring the latest version is being used. Thank you for your attention to this matter.
Have you had a chance to update the code and delete any local images? It's an important step in ensuring the latest version is being used. Thank you for your attention to this matter.
I did, currently using:
image:
repository: ghcr.io/openimsdk/openim-admin-front
pullPolicy: Always
tag: "latest"
Access through {my_host}/openim-admin-front/login.
FYI, I did use Aliyun LB instead of Nginx Ingress. But I doubt this is relevant
Hi, any updates on this?
It seems like this issue has already been resolved. Could you please try using the latest image?