Closed argetlam-coder closed 2 years ago
I havent ran into an issue like that. Ill see about creating a new environment with a fresh install. Can I get the base OS and docker version your using?
My docker and docker-compose versions are:
Docker version 20.10.12, build e91ed57
docker-compose version 1.29.2, build 5becea4c
My base OS is Kali Linux Version 2021.4
. It's based on Debian and uses the following kernel: 5.14.0-kali4-amd64
. This is a virtual machine, which I use to test all sorts of things. I have not yet tested it on my productive system.
I have now also tested it in my production system (Debian). There are problems with the name resolution here as well. I have created the following php script for testing:
<?php
$ip = gethostbyname("node.example.com");
echo $ip;
?>
The command gethostbyname
is used by Pterodactyl, when creating a new node. This fails for me at the moment, because it cannot resolve the FQDN.
If I execute this script in the console inside the container, it works without problems. If the webserver executes this command when creating a node, then it fails.
Hm, I haven't encountered this issue yet when deploying this, and I've recently setup a fresh installation on an EL based host. Have you made any changes to the image or docker compose file? It should just work with the stock configuration of the repo.
Yes I have made changes to the image and to the docker compose file. I must have an error in my changes then . I just thought it was a general problem. In the meantime I got pterodactyl running with the official images on my server. Thanks a lot for your help.
When I call the web interface in the browser, I get error 500.
In the laravel log I see the following error:
I took a closer look at this error and it looks like in one of the PHP libraries the DNS name resolution is not working properly. This problem concerns the connection to the database and to redis.
I have run
ping cache
from inside the panel container and it has worked. It seems that only php or one of the libraries is not able to resolve the name.As a workaround I created an additional network in the docker-compose file, added all services to this network and then gave the cache and the mysql service a fixed ip. Then I configured the corresponding ip addresses for the services in the
panel.env
. Now I can access the web interface.