#Having issues controlling pterodactyl with api key

39 messages · Page 1 of 1 (latest)

rotund bolt
#

Hello i am using Paymenter and trying to have it create servers when i get plans. I have encountered some errors on the ptero side and it wont create the servers.

I had this error

Next Pterodactyl\Exceptions\Http\Connection\DaemonConnectionException: An error occurred on the remote host: There was an error while communicating with the machine running this server. This error has been logged, please try again. (code: 400) (request_id: ). (request id: ) in /var/www/pterodactyl/app/Repositories/Wings/DaemonConfigurationRepository.php:43
Stack trace:

and then was advised to use systemctl status wings which gave me this error

ERROR: [Jun  9 01:45:22.600] sftp: failed to accept inbound connection error=EOF ip=199.45.154.126:47926

And on the web console i got this error

nodes:1  Access to XMLHttpRequest at 'https://panel-nylon.econome.uk:8080/api/system' from origin 'https://panel-nylon.econome.uk' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://panel-nylon.econome.uk/' that is not equal to the supplied origin.
granite mica
#

For the last error, you need to correct the remote: in your wings config and the APP_URL in your .env file. Remove the trailing /

wraith streamBOT
#

The env file can be found at /var/www/pterodactyl/.env. Files starting with a . in Linux are hidden so it may not show up in file browsers by default. You can open it directly with nano /var/www/pterodactyl/.env

granite mica
#

systemctl status wings isn't useful when you cut out all the information and show only a single irrelevant log entry. The point is to check the status of the service to see if it's up.

wraith streamBOT
#

We need some logs from you in order to help debug this issue.
Panel: tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
Wings: sudo wings diagnostics
Please see .plogs and .wlogs respectively for more information.

rotund bolt
#

i have ensured everything is fine, and the required ports are accessible.

wraith streamBOT
#

I have found the following for: https://media.discordapp.net/attachments/1381427689856172193/1381432024320966676/Screenshot_253.png?ex=68477e54&is=68462cd4&hm=014555178e8d54a7855c4379849454dc2bb20f199c88ce67a76a80679dced635&
The env file can be found at /var/www/pterodactyl/.env. Files starting with a . in Linux are hidden so it may not show up in file browsers by default. You can open it directly with nano /var/www/pterodactyl/.env
I have found the following for: https://media.discordapp.net/attachments/1381427689856172193/1381432024773955696/Screenshot_254.png?ex=68477e54&is=68462cd4&hm=b04450c3bc8e57798b11526c5458b9613b2cd40dac7f7dd92133b83a42443ded&
@rotund bolt It looks like you are having issues with connecting to Wings.

Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php

Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors

Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.

granite mica
#

good. Now those logs that were asked for

rotund bolt
#

i think something is connecting to the ports before the wings can? but im unsure what all i have on this server are ptero and its wings + all its dependencies

wraith streamBOT
#

I have found the following for: https://media.discordapp.net/attachments/1381427689856172193/1381433036708642966/Screenshot_255.png?ex=68477f45&is=68462dc5&hm=5f3363c921130fa3d5c8d0f11cdbb42ae474dae068c79bc54ecef0cd84c9c6cb&
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

I have found the following for: https://media.discordapp.net/attachments/1381427689856172193/1381433037299912776/Screenshot_256.png?ex=68477f45&is=68462dc5&hm=d28139b000b6ced43edaa4714749f2d48602f06e804b3ffc2be87a5f5d04920c&
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

rotund bolt
granite mica
#

Let me know when you're willing to get those logs we asked for

rotund bolt
#

k

granite mica
#

Send the link - Please don't dump the entire report in the channel.

rotund bolt
wraith streamBOT
#

I have found the following for: https://ptero.co/aneziyecah
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

rotund bolt
granite mica
#

You flooded your wings logs with those errors because you kept trying to start wings when it was already running

rotund bolt
granite mica
#

Sure...

rotund bolt
#

cheers for the help

rotund bolt
#

GNU nano 7.2 /etc/pterodactyl/config.yml

  transfers:
    download_limit: 0
  openat_mode: auto
docker:
  network:
    interface: 172.18.0.1
    dns:
    - 1.1.1.1
    - 1.0.0.1
    name: pterodactyl_nw
    ispn: false
    driver: bridge
    network_mode: pterodactyl_nw
    is_internal: false
    enable_icc: true
    network_mtu: 1500
    interfaces:
      v4:
        subnet: 172.18.0.0/16
        gateway: 172.18.0.1
      v6:
        subnet: fdba:17c8:6c94::/64
        gateway: fdba:17c8:6c94::1011
  domainname: ""
  registries: {}
  tmpfs_size: 100
  container_pid_limit: 512
  installer_limits:
    memory: 1024
    cpu: 100
  overhead:
    override: false
    default_multiplier: 1.05
    multipliers: {}
  use_performant_inspect: true
  userns_mode: ""
  log_config:
    type: local
    config:
      compress: "false"
      max-file: "1"
      max-size: 5m
      mode: non-blocking
throttles:
  enabled: true
  lines: 2000
  line_reset_interval: 100
remote: https://panel-nylon.econome.uk
remote_query:
  timeout: 30
  boot_servers_per_page: 50
allowed_mounts: []
allowed_origins: []
allow_cors_private_network: false
ignore_panel_config_updates: false

is this all correct? really struggling to workout what the problem is here

granite mica
#

Unfortunately we can't help people who refuse to cooperate

rotund bolt
#

what? I have done everything you asked dude

granite mica
#

You still haven't provided the logs that were asked for

rotund bolt
#

I sent what I assumed where the logs you wanted and you never said if those where the right ones or not?

granite mica
#

You were told what logs we wanted

#

I never said more because I waited for you to send the rest

rotund bolt
#

You never specified which logs you wanted lmao

If there's more you want you actually gotta help out and tell me what you need.

granite mica
#

Thats bullshit

granite mica
#

You were asked multiple times for logs but you don't seem to want to do it

rotund bolt
#

i sent the diagnostics and all the errors in the laravel if you needed more you simply had to ask idk why you have to be such an ass about it :/

theres the other log, it doesnt give a link for me to send so i have to send it like this

granite mica
#

I get tired of asking for logs over and over again and you just ignoring it.

#

The log command gives you a url. I've already asked you not to dump giant logs in here.

#

If you're not getting a url you either messed up the command, or you have a network issue.