500 Error on /admin/servers/new

[Verox001]

Current Behavior

When having more than 26921 allocations present in the database, the site simply will drop a 500 error. No error in the Laravel logs is present.
The bug might occur for even lower numbers of present allocations, but I didn't test out what's the limit.

Expected Behavior

It should load the page for server-creation.

Steps to Reproduce

Insert more than 26921 Allocations in the table. In my case I had 3 nodes, with each having ports from 1025-9999.
Visit the server creation page "/admin/servers/new" and there it is.

The problem is probably that the Allocations aren't paginated in the server creation and update menu, so it exceeds the PHP Sending Limit or anything else, which results in the 500 Error.

Panel Version

1.11.5

Wings Version

1.11.8

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

No response

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
• I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.

[Boy132]

If you get a 500 server error but no logs you most likely have wrong file permissions.
After you fixed your file permissions post logs. (you can find info about that in the docs or on the discord)

I just tested with ~15000 allocations and it worked fine.

[Verox001]

I can access everything else and errors (like an initial Redis Connection Error) have been logged correctly. Please try with at least 26000 allocations. On the discord other people already had the same problem.

[Verox001]

To prove the error furthermore. When I delete the allocations, the creation page is working just fine.

[Boy132]

I now tried with ~29000 allocations and it worked fine.

[Verox001]

Okay and what might be the issue then? Maybe it has to do with the request max_size set in PHP settings?

[Boy132]

Just to clarify, do you see a HTTP ERROR 500 or 500 | SERVER ERROR?

[Verox001]

Not the Laravel 500 Error, but the one from the actual server:

[Boy132]

Not the Laravel 500 Error, but the one from the actual server:

Okay. In that case you need to check your webserver logs.
For nginx: tail -n 150 /var/log/nginx/pterodactyl.app-error.log | nc pteropaste.com 99 and share the link.

[Verox001]

I'm on Apache. Could you please tell me the location where to find them, if you know them?

[Boy132]

Probably something like /var/log/apache2.

[Verox001]

Nothing noticable in /var/log/apache2/error.log. The last error occured a few days ago and had nothing to do with the panel.

[Verox001]

Could you try to open the allocation menu and tell me if ALL allocations are included in there?

[Boy132]

Could you try to open the allocation menu and tell me if ALL allocations are included in there?

It shows all allocations. (1025 - 29999)

[Verox001]

Okay, I will try enabling Apache debug to get some insights.

[Verox001]

Found it: It was located in the PHP FPM Logs:
PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 20480 bytes) in /var/www/htdocs/pterodactyl/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 421

[Verox001]

I set the memory_limit to 4 GB and now it's loading the page, but the loading time is longer than 30 seconds. I would say pagination is required to solve this problem, but you're the expert.

[Boy132]

[...] but the loading time is longer than 30 seconds. I would say pagination is required to solve this problem [...]

It takes a couple seconds for me as well. I guess that's kinda normal for this many allocations.
But v2 will rework the admin ui anyways so the loading time will probably be improved there.