starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #4727] [Bug]: PaperMC Api Url endpoint modified #2936

New issue

Closed

opened 2026-02-27 03:06:23 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 03:06:23 +03:00

Owner

Originally created by @Neimolon on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4727

User story

As a user, I experienced error updating server throug pmcserver command who crashes the server instance

Game

PaperMC

Linux distro

Ubuntu 22.04

Command

command: update

Further information

https://papermc.io/api/v2/projects:

The PaperMC URL which privedes build info has changed... need to be updated to: https://api.papermc.io/v2/projects

Fix:

Relevant log output

linuxgsm@a81cd16d04e0:/app$ ./pmcserver update
[  OK  ] Updating pmcserver: Checking local build: papermc.ioparse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
[  OK  ] Updating pmcserver: Checking for update: papermc.io

Steps to reproduce

go to app directory and launch ./pmcserver update
Outputs this error:

linuxgsm@a81cd16d04e0:/app$ ./pmcserver update
[ OK ] Updating pmcserver: Checking local build: papermc.ioparse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
[ OK ] Updating pmcserver: Checking for update: papermc.io

Originally created by @Neimolon on GitHub (Jan 2, 2025). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4727 ### User story As a user, I experienced error updating server throug pmcserver command who crashes the server instance ### Game PaperMC ### Linux distro Ubuntu 22.04 ### Command command: update ### Further information https://papermc.io/api/v2/projects: ![image](https://github.com/user-attachments/assets/2a03994a-eb40-4f3c-be59-240f09d0583f) The PaperMC URL which privedes build info has changed... need to be updated to: https://api.papermc.io/v2/projects Fix: ![image](https://github.com/user-attachments/assets/330e48b5-96ee-432f-8588-2c8877c50561) ### Relevant log output ```shell linuxgsm@a81cd16d04e0:/app$ ./pmcserver update [ OK ] Updating pmcserver: Checking local build: papermc.ioparse error: Invalid numeric literal at line 1, column 10 parse error: Invalid numeric literal at line 1, column 10 parse error: Invalid numeric literal at line 1, column 10 parse error: Invalid numeric literal at line 1, column 10 [ OK ] Updating pmcserver: Checking for update: papermc.io ``` ### Steps to reproduce 1. go to app directory and launch ./pmcserver update 2. Outputs this error: linuxgsm@a81cd16d04e0:/app$ ./pmcserver update [ OK ] Updating pmcserver: Checking local build: papermc.ioparse error: Invalid numeric literal at line 1, column 10 parse error: Invalid numeric literal at line 1, column 10 parse error: Invalid numeric literal at line 1, column 10 parse error: Invalid numeric literal at line 1, column 10 [ OK ] Updating pmcserver: Checking for update: papermc.io

kerem

2026-02-27 03:06:23 +03:00

closed this issue
added the
type: bug

distro: Ubuntu

command: update
labels

kerem commented

2026-02-27 03:06:25 +03:00

Author

Owner

@Jakesta13 commented on GitHub (Jan 7, 2025):

Just adding my comment here to also express how flipping annoying this change to their API URL was.

PaperMC literally had no reason to do this other than trying to make a point, which causes issues like these unnecessary.

Broke my own private server and it took me embarrassingly long to figure out why it broke (I kept thinking my own scripting unrelated to PaperMC was just broken as I had updated it the night before the API change and the server was set to update the next day...)

@Jakesta13 commented on GitHub (Jan 7, 2025): Just adding my comment here to also express how flipping annoying this change to their API URL was. PaperMC literally had no reason to do this other than trying to make a point, which causes issues like these unnecessary. Broke my own private server and it took me embarrassingly long to figure out why it broke (I kept thinking my own scripting unrelated to PaperMC was just broken as I had updated it the night before the API change and the server was set to update the next day...)

kerem commented

2026-02-27 03:06:25 +03:00

Author

Owner

@ben-2357 commented on GitHub (Jan 7, 2025):

I would also like to add that there is a cron entry already in the container:

*/60 * * * * /app/pmcserver update > /dev/null 2>&1

I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks!

@ben-2357 commented on GitHub (Jan 7, 2025): I would also like to add that there is a cron entry already in the container: ```bash */60 * * * * /app/pmcserver update > /dev/null 2>&1 ``` I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks!

kerem commented

2026-02-27 03:06:25 +03:00

Author

Owner

@Jakesta13 commented on GitHub (Jan 10, 2025):

I would also like to add that there is a cron entry already in the container:
*/60 * * * * /app/pmcserver update > /dev/null 2>&1
I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks!

Best to make issues as it helps organize and track, vs having an issue commented inside an unrelated issue.

@Jakesta13 commented on GitHub (Jan 10, 2025): > I would also like to add that there is a cron entry already in the container: > > ```shell > */60 * * * * /app/pmcserver update > /dev/null 2>&1 > ``` > > I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks! Best to make issues as it helps organize and track, vs having an issue commented inside an unrelated issue.

kerem commented

2026-02-27 03:06:25 +03:00

Author

Owner

@ben-2357 commented on GitHub (Jan 10, 2025):

I would also like to add that there is a cron entry already in the container:
*/60 * * * * /app/pmcserver update > /dev/null 2>&1
I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks!
Best to make issues as it helps organize and track, vs having an issue commented inside an unrelated issue.

Will do!

@ben-2357 commented on GitHub (Jan 10, 2025): > > I would also like to add that there is a cron entry already in the container: > > ```shell > > */60 * * * * /app/pmcserver update > /dev/null 2>&1 > > ``` > > > > > > > > > > > > > > > > > > > > > > > > I don't know if this is intentional, but it is very annoying because I'd like to set my own update interval without having to modify the actual application code. I didn't think it was necessary to make an issue for such a small problem. Thanks! > > Best to make issues as it helps organize and track, vs having an issue commented inside an unrelated issue. Will do!

kerem commented

2026-02-27 03:06:25 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 16, 2026):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Feb 16, 2026): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.