#HTTP error 500 while install

1 messages · Page 1 of 1 (latest)

daring igloo
#

i installed ctrlpanel but during the setup (/install) at /install/forms.php it rediricts and shows this 500 Error

weak ironBOT
#

How to get support?

  • Search for similar posts first!
  • What have you tried already?
  • Where the error has happened?
  • Provide logs!

Dont's (will get you muted):

  • Post some image or text without context.
  • Post a command you ran without the output,
  • Post just the output.
  • Reply with "i already did that" (See: How to get Support)
  • Post every word as a new message.
  • Ping Staff.
  • Post the same message in multiple channels.

Get Logs:
Laravel / CP.GG: tail -n 100 /var/www/controlpanel/storage/logs/laravel.log | nc pteropaste.com 99
Installer: tail -n 100 /var/www/controlpanel/public/install/logs/installer.log | nc pteropaste.com 99
(NGINX: Are usually in /var/log/nginx/ and got the (sub)domain in the name. There are error and access logs)

daring igloo
#

here are the logs

errant loom
#

Send installer logs

daring igloo
#

no /logs folder

#

nginx config

#

ctrlpanel.conf

errant loom
daring igloo
weak ironBOT
errant loom
#

#💬┃general message

#

Read this

daring igloo
#

now need to reboot mysql?

errant loom
#

Yes, and try finish install again

daring igloo
#

thanks

errant loom
#

MariaDB broke almost all php applications)

#

If there are any other problems, please contact

daring igloo
#

at the step where i need to put api keys

weak ironBOT
#

Can you please fetch the error logs, so we can assist you better regarding this error.
tail -n 100 /var/www/controlpanel/public/install/logs/installer.log | nc pteropaste.com 99

daring igloo
#

is may that be my problem on my router that dosent support ip looop back?

#

in fact i cant install the pterodactyl panel and wings on the same vm

daring igloo
#

wait

#

seems woriking

#

dosent let me login @errant loom

weak ironBOT
errant loom
#

Have you finished the web installation?

daring igloo
#

i put my admin credentials that are the same on ptero but simply reloads this page

errant loom
#

You must use the email and password that you set during the web installation

daring igloo
errant loom
#

This means that you have not finished the installation, if you have an error, it does not mean that the installation is complete

daring igloo
#

when i try to register

#

but it says that the mail hasbeen taken

errant loom
#

Send installer logs

daring igloo
#

... when i reload

daring igloo
errant loom
daring igloo
#

wait, now it says when i try to login that the credentials are wrong

#

Nginx

weak ironBOT
daring igloo
#

so when i try to login whit the username and password it reloads the page, when i try to login whit email and password says wrong credentials

errant loom
#

Check that the pterodactyl ssl certificate is up-to-date and has not expired

daring igloo
errant loom
#

Then I would advise you to clear the database, and try to go through the web installation stage again

daring igloo
#

how can i clear the database?

errant loom
#

You should not attempt to create an account yourself until you have completed the web installation.

daring igloo
#

what is the table name in the db?

errant loom
#
DROP DATABASE controlpanel;
CREATE DATABASE controlpanel;```
daring igloo
#

did

errant loom
#

Try go to /install again

daring igloo
errant loom
daring igloo
#

ok

#

is taking long to load, it may be of the loop back problem?

errant loom
#

No

#

cpgg accesses pterodactyl by domain

daring igloo
#

same at forms.php

errant loom
#

Do u use Cloudflare?

daring igloo
errant loom
#

Does Pterodactyl work, and is it accessible?

daring igloo
#

it may be because it is a container in proxmox and not a vm?

errant loom
#

The error message "SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share)" indicates a problem during SSL handshake between the client (IP address 80.82.77.202) and the server on port 443 (0.0.0.0). The "bad key share" error typically occurs due to incompatible keys or encryption parameters between the client and server.

To resolve this issue, you may need to take the following actions:

  1. Check SSL/TLS configuration on the server: Ensure that the server has the correct keys, certificates, and encryption parameters configured.

  2. Update OpenSSL version: Make sure the server is using an up-to-date version of OpenSSL, as older versions may cause compatibility issues.

  3. Check encryption compatibility: Verify that the client and server support common encryption algorithms and key parameters.

  4. Logs and debugging: Review detailed SSL/TLS logs on the server to gather more information about the issue. You may need to enable additional debugging to pinpoint the cause of the error.

If the issue persists after these steps, you may need to consult with security experts or technical support for a more thorough analysis and resolution of the problem.

daring igloo
#

huh

#

it isent possible...they are on the same vm & installed them togheter today whit ssl