Proxy image not working due to paper api endpoint change

[Andrei965]

What happened?

The proxy image is currently not working because Paper recently changed their API. The Velocity JAR, previously located at https://papermc.io/api/v2/projects/velocity, has been moved to https://api.papermc.io/v2/projects/velocity.

Although the itzg/mc-proxy Docker image has been updated to address this change, no new release has been made yet, which is why Renovate did not automatically update it. The fix is available in the latest tag of the image.

To prevent similar issues in the future, I recommend making the spec.template.spec.version.name property functional in the proxy fleet configuration, ensuring it overwrites the Docker image version tag as needed.

Related Commit:
Commit fixing the API endpoint change

What components are involved in your issue?

Operator

Version

v0.11.0

Kubernetes Version

Client Version: v1.30.5 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.31.0

Relevant log output

[init] Resolving type given VELOCITY
[mc-image-helper] 13:45:05.458 ERROR : 'get' command failed. Version is 1.37.0
me.itzg.helpers.get.RequestFailedException: Failed to download https://papermc.io/api/v2/projects/velocity: status code: 403, reason phrase: Forbidden
 at me.itzg.helpers.get.GetCommand.processSingleUri(GetCommand.java:442)
 at me.itzg.helpers.get.GetCommand.call(GetCommand.java:188)
 at me.itzg.helpers.get.GetCommand.call(GetCommand.java:55)
 at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
 at picocli.CommandLine.access$1500(CommandLine.java:148)
 at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
 at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
 at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
 at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
 at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
 at picocli.CommandLine.execute(CommandLine.java:2170)
 at me.itzg.helpers.McImageHelper.main(McImageHelper.java:157)
Caused by: org.apache.hc.client5.http.HttpResponseException: status code: 403, reason phrase: Forbidden
 at org.apache.hc.client5.http.impl.classic.AbstractHttpClientResponseHandler.handleResponse(AbstractHttpClientResponseHandler.java:68)
 at me.itzg.helpers.http.LoggingResponseHandler.handleResponse(LoggingResponseHandler.java:20)
 at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:247)
 at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:188)
 at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:162)
 at me.itzg.helpers.get.GetCommand.processSingleUri(GetCommand.java:440)
 ... 11 common frames omitted
ERROR: failed to lookup PaperMC versions

Code of Conduct

• I agree to follow this project's Code of Conduct

[Acemavie234]

Is there a way I could fix this myself? I am trying out shulker right now but I am running into the same issue. Or do I have to wait until shulker fixes it itself?

[Andrei965]

Hi @Acemavie234 ! The itzg docker image proxy has made a release fixing the issue yesterday. If you want, you can download the source code, and, in the shulker operator package, look for a file called constants.rs. In there you can edit the version tag of the proxy image. After that, you will have to build the shulker operator docker image and run it on your cluster.

[Acemavie234]

Funnily enough I made a issue on the repository asking them to make a release including the new API change, but good to see this fixed now

[jeremylvln]

There is already a MR that bumps the version. Will look into that ASAP.

[jeremylvln]

Whoops, that was closed automatically. I've confirmed locally that using the new itzg's image fixes the issue. I've started a release that should be available soon :)

Thanks for your patience!

[jeremylvln]

Fix released in 0.12.0 :)

[Acemavie234]

Okay, I'll try it soon. I figured that I can change the docker image on the bottom of the yaml file but I had some kind of networking issues