-
Notifications
You must be signed in to change notification settings - Fork 31
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
Returns 404 when running on azure app service #114
Comments
Hi @naramck Please make sure of the access token used for the proxy can read those projects. curl --request GET --header "PRIVATE-TOKEN: <TOKEN_USED_BY_BACKSTAGE_PROXY_FOR_GITLAB>" https://gitlabhost.com/api/v4/projects/<project_id> |
@naramck were you able to resolve the issue?. |
Hi @satrox28, |
This seems to be an issue with proxy plugin. The url that is being sent to proxy from browser (GitlabCIClient) is shown as |
Hi @naramck Can you change it to project id in annotation and try. |
Hi @naramck |
HI @satrox28, |
were you able to check if the below proxy config for gitlabci exist on app-config.yaml?.
|
@satrox28 yes, i have the correct config and token. |
I added the plugin to a backstage instance running on azure app service as docker container. The plugin returns 404 hitting
https://my.domain.com/api/proxy/gitlabci/projects/gitlabgroup%2Fprojectname.
I verified the proxy works fine when I hit https://my.domain.com/api/proxy/test which goes to example.com.
I am seeing in the logs that returned 404 the url shown as https://my.domain.com/api/proxy/gitlabci/projects/gitlabgroup/projectname. I am not sure if the forward slash is the issue.
It works locally on my machine when using separate port for backend. Can you please let me know if there is anything I have to do for running this plugin?
thank you.
The text was updated successfully, but these errors were encountered: