Error following blueprint docker guide
I am getting this error:
When using the guide here: https://github.com/BlueprintFramework/web-rewrite/blob/master/apps/frontend/content/guides/docker/install.md
I got that when trying to add the location, I followed the guide almost exactly (only thing I changed was the wings stuff in .env because it put
\n into it instead of going to the next line40 Replies
What does your compose file look like?
its the exact one from the link on that page I sent
What do the logs from your database say?
Just realised this got a response, here are the logs
oh wait what
it suddenly worked
even though I never changed anything from then
super weird
ok new issue
localhost returns PR_END_OF_FILE_ERROR
What does your panel.conf file look like? It's at /srv/pterodactyl/nginx by default.
Check panel logs for info as well, and the health status with
docker compose pshere is my panel.conf
here is the output for
docker compose ps
this is the end of the panel logs#WARN[0000] The "AUTO_ALLOCATION_START_PORT" variable is not set. Defaulting to a blank string. WARN[0000] The "AUTO_ALLOCATION_END_PORT" variable is not set. Defaulting to a blank string. WARN[0000] The "EGG_AUTHOR_EMAIL" variable is not set. Defaulting to a blank string. WARN[0000] The "APP_2FA_REQUIRED" variable is not set. Defaulting to a blank string. WARN[0000] The "AUTO_ALLOCATION" variable is not set. Defaulting to a blank string. WARN[0000] The "AUTO_ALLOCATION_START_PORT" variable is not set. Defaulting to a blank string. WARN[0000] The "AUTO_ALLOCATION_END_PORT" variable is not set. Defaulting to a blank string. WARN[0000] The "EGG_AUTHOR_EMAIL" variable is not set. Defaulting to a blank string. WARN[0000] The "AUTO_ALLOCATION" variable is not set. Defaulting to a blank string. WARN[0000] The "APP_2FA_REQUIRED" variable is not set. Defaulting to a blank string.Start from the example .env file here: https://github.com/BlueprintFramework/docker/blob/Master/.env The docs you followed are experimental right now; refer to the README.md file in that repo instead.
I will add those, but I don't really see how they would be vital to the panel being accessible
Added them, still same result
wings is failing to start with this
both panel and wings are stuck in starting state, panel is not doing anything and I dont see any issues in logs
this is still the only thing showing in panel logs
well, aside from the other normal stuff like updating eggs and stuff
Have you taken the stack down and up, or are you just restarting it?
Now that the env vars are in:
I did take it down and put it back up when I said this
I'd recommend starting over completely and just going off the Github Repo's README file. It will most likely just work out of the box after that.
I mean I can try it but last time I tried that it didn't work
Just make sure you're starting from scratch. Take the volume down (
docker compose down -v), delete the bind mounts. Should be a blank /srv/pterodactyl directory with docker-compose.yml and .envexact same error doing what is said in the readme
PR_END_OF_FILE_ERROR
same log output
this is my env
PANEL_PORT is set to 443, but your panel.conf file for Nginx is pointed to 80 going off the last one you sent. If you mean to use TLS encryption, change <domain> and drop this in it's place:
If you don't mean to (I see you have http://localhost set), change
PANEL_PORT to 80.
Also, to prevent your logs getting spammed with meaningless errors, change MAIL_DRIVER to array to effectively disable it.changing it to 80 seems to have fixed it, I feel silly now for not noticing that sooner 😅
I missed it too, to be fair
Also, do you know a way I could run multiple instances of this on the same machine? When I tried I got the error "failed to create network pool overlaps with other one on this address space"
The subnet chosen in your docker-compose.yml file can't be used, and the subnet chosen for pterodactyl_nw in your Wings config.yml file also can't be used.
You can see what's currently used with
ip awhere is the config.yml supposed to be for wings? I can't find it anywhere
put it in the /wings folder and its recognised it, but now my wings logs get this
Wings is in it's own container; localhost will point INSIDE the Wings container at port 80, which has nothing there. Use the machine's address, e.g. 192.168.X.X for the Wings FQDN. If you plan to access the panel from a different machine on your network, use that for the panel FQDN as well.
Ah I see, is there any way I could do it so that it would work across different networks without having to change any configs? I'm setting this up on my laptop and will be switching networks a lot, and the assigned IP will be different in each network
im not hugely knowledgable in networking 😅
would setting it to something like
172.17.0.1 work? I saw it was still there even if I disconnected from wifi
hmm seems like that is a no, tried it and got this error
Yes, you can set it up at your public IP and port forward, or you can set up a basic VPN at your public IP that you connect to to get to your services, or you can use a Cloudflare Tunnel if you're ok with learning how they work, and accepting the limitations, like no uploads bigger than 100MB, and consequently transferring servers between nodes, you'd need to empty out the server files first since it transfers over WebRTC and is subject to the 100MB limit. 3 options, varying levels of complexity.
Locally, it has to be a different network. You can connect to that network from anywhere using a VPN, port forward, or proxy.
I think you misunderstood, I am running the docker compose on my laptop and it is the laptop that is switching between networks
Are you only CONNECTING to your panel from the laptop as well?
Also my college blocks VPNs, no clue how though
yeah I am
You can use the Docker Network gateways as the FQDN addresses then. 172.20.0.1 by default for the panel and Wings stack.
just tried that and I am still getting this error for some reason
Also not sure if this affects anything, but I set the FQDN to
fileplus.ptero and have that pointing to 172.20.0.1 in hostsThat's fine, that's the same as using 172.20.0.1 directly as far as everything here is concerned.
What is the result of
ip a?
What does your network section of the config.yml file look like?
I assume that's from Wings logs, not something that pops up when you bring the panel stack up.Yeah its wings logs, ill check
ip a and send the config tomorrow since its super lateWhen you do, you should see a bunch of subnets. Typically, you'll just go into the config.yml file, change the subnet from 172.18.0.0/16 to one not in use, and change the gateway and interface to match (the first address in the subnet, e.g. 172.18.0.1 by default for both of them).