Check utf-8 locales before script installation

[pafade89]

Is your feature request related to a problem? Please describe.

It would be very useful to query the locales in the script and if incorrect, switch to UTF-8 to ensure that Nginx receives its configuration and the /var/www/pterodactyl folder is created.

Describe the solution you'd like

Same as above I find the feature request meaningful, as there have been several issues related to this in the repository both currently and in the past.

Example: #445 #436

[Linux123123]

Nginx in this case is completly unrelated. I do not see how setting locales would fix the issue, with database password. The issue with it is commonly special characters, character which don't get escaped and such which cause issues while creating the user. The best solution would be to have a regex for mysql password.

[pafade89]

I tried to install Pterodactyl with the script, which didn't work properly. It works only when I adjusted the locales to UTF-8 that your script ran smoothly.

[vilhelmprytz]

The linked issues do not seem to be relevant to the issue you have opened. There is not enough information to debug this, can you clarify what went wrong and what you did to remedy it?

[pafade89]

It is difficult to provide you with log files in this case, as your script runs without errors. However, no Nginx configuration is carried out, and the entire Pterodactyl data is not transferred. If you change the locale from C POSIX (ASCII) to the UTF-8 locale, then the script runs without errors again. This time, the Nginx configuration is made, and the Pterodactyl data is transferred correctly. The server starts thereafter and runs as expected.

The entire process was tested multiple times on a freshly installed Debian system with no prior configuration. Only the net install of Debian was performed.

Thank you in advanced

P

[vilhelmprytz]

Interesting. It would be good however to check the logs, specifically script logs. Could you include the logs here?

Script logs:

cat /var/log/pterodactyl-installer.log | nc termbin.com 9999

Panel logs:

tail -n 100 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc bin.ptdl.co 99

Daemon logs:

sudo wings diagnostics --debug

[pafade89]

Interesting. It would be good however to check the logs, specifically script logs. Could you include the logs here?

Script logs:

cat /var/log/pterodactyl-installer.log | nc termbin.com 9999

Link: https://termbin.com/0d50

Panel logs:

tail -n 100 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc bin.ptdl.co 99

As I stated before the pterodactyl folder isn't created:

root@test:/# tail -n 100 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc bin.ptdl.co 99
tail: cannot open '/var/www/pterodactyl/storage/logs/laravel-2024-03-14.log' for reading: No such file or directory

Daemon logs:

sudo wings diagnostics --debug

As expected wings has no configuration file:

root@test:/# wings diagnostics --debug

Error: Configuration File Not Found

Wings was not able to locate your configuration file, and therefore is not
able to complete its boot process. Please ensure you have copied your instance
configuration file into the default location below.

Default Location: /etc/pterodactyl/config.yml

This is not a bug with this software. Please do not make a bug report
for this issue, it will be closed.

[vilhelmprytz]

Sorry for the delay in this. I think the termbin link expired. If this is still an issue, can you upload the logs again from the installation process?

[pafade89]

@vilhelmprytz No problem. Here is the new upload.

https://termbin.com/qa0g

pterodactyl is not being created.

[pafade89]

I think this is no longer necessary with the new pelican panel.