Template Repo: https://github.com/Mainfrezzer/UnRaid-Templates
 

App: Adguard Home with Unbound https://adguard.com/adguard-home/overview.html & https://www.nlnetlabs.nl/projects/unbound/about/

Docker Hub: https://hub.docker.com/r/mainfrezzer/adguardhome

Github: https://github.com/Mainfrezzer/adguardhome-unbound
Docs: https://github.com/adguardteam/adguardhome/wiki/Configuration & https://nlnetlabs.nl/documentation/unbound/unbound.conf/

 

App: ArchiveBox https://archivebox.io/

GitHub: https://github.com/ArchiveBox/ArchiveBox

Docs: https://github.com/ArchiveBox/ArchiveBox/wiki

 

App: Pelican Panel & Pelican Wings https://pelican.dev/

GitHub: https://github.com/pelican-dev

Docs: https://github.com/pelican-dev/docs

Including the modified variants:
Mainfrezzer-Pelican-Panel & Mainfrezzer-Pelican-Wings

https://hub.docker.com/r/mainfrezzer/pelican-panel/ & https://hub.docker.com/r/mainfrezzer/pelican-wing/

GitHub: https://github.com/Mainfrezzer/Mainfrezzer-Pelican-Panel & https://github.com/Mainfrezzer/Mainfrezzer-Pelican-Wing

App: Roundcubemail https://roundcube.net/
Docker Hub: https://hub.docker.com/r/roundcube/roundcubemail/
GitHub: https://github.com/roundcube/roundcubemail-docker

App: mitmproxy https://mitmproxy.org/
Docker Hub: https://hub.docker.com/r/mitmproxy/mitmproxy/
GitHub: https://github.com/mitmproxy/mitmproxy

Docs: https://docs.mitmproxy.org/stable/

App: GPTWOL https://github.com/Misterbabou/gptwol

Docker Hub: https://hub.docker.com/r/misterbabou/gptwol

 

App: Wireguard-Client https://github.com/Mainfrezzer/wireguard-bridge

App: Bashupload https://github.com/IO-Technologies/bashupload
Github: https://github.com/Mainfrezzer/docker-bashupload

 

 

Edited March 20, 20251 yr by Mainfrezzer
added Github repos

Hello there,

 

How are you ?

 

Thanks for this and sorry the ignorance, but where I have to put this address 127.0.0.1:8053 ?

 

Please see the capture attached.

 

Is there ? Or where ?

 

Any help is very welcome.

 

Thanks.

 

Regards.

 

 

8 minutes ago, Arkdale said:

Hello there,

 

How are you ?

 

Thanks for this and sorry the ignorance, but where I have to put this address 127.0.0.1:8053 ?

Im good, how are you?

 

 

The ip is only used after you finished the Installation process. you get redirected to the login page. After you logged in, you can enter the ip in the DNS settings

 

 

Edit: i just noticed that you changed the DNS port to 8053, you need to change that back to 53

Edited December 18, 20241 yr by Mainfrezzer

Thanks. I will do it.

 

I am good, too. Thank you.

 

Regards.

Edited December 18, 20241 yr by Arkdale

Concerning the unbound, doesn't adguard have the ability to do DOH/DOT without it? Whats the use case advantage to Unbound?

Mostly privacy since you dont interact with 3rd parties that you need to trust, i.e. Google etc. Unbound asks the rootservers directly. 

Hey, thanks for the pelican templates, just I dont het it running. Could you add some details, I understood

 

1. install panel and since i use nginx as reverse proxy restart with caddy file

2 open http://container.ip/installer -> cant reach it 

3 copy the config.yaml to the wings? -> is created after install?

4. edit config.yml

5 start wings

 

Thanks appreciate it.

Same as Dr.Goyo here. No Config.yaml is created in prescribed folder. I also am unable to connect to the Installer WebGUI, just receive the "ERR_CONNECTION_REFUSED". What are we missing?

 

 

if you kept the mapping for the reverse proxy in the template. You need to manually add the Caddyfile into your location you chose

 

{
    admin off
    email {$ADMIN_EMAIL}
}

:80 {
    root * /var/www/html/public
    encode gzip

    php_fastcgi 127.0.0.1:9000
    file_server
}

The Config.yml isnt created as a file, its displayed in the webui once you added the node.


you manually have to create that one for the wing with the contents of it.

Edited December 20, 20241 yr by Mainfrezzer
remove a stray "the"

AdGuard container fails to start with the following error "DNS Resolution Error. Start the container with --dns=1.1.1.1 or 8.8.8.8"

27 minutes ago, stayupthetree said:

AdGuard container fails to start with the following error "DNS Resolution Error. Start the container with --dns=1.1.1.1 or 8.8.8.8"

How are you running that container? Ipv6 only on br0 or something else?

I did include a test to check if the container is able to download the roothints and should only shutdown when it fails to ping "www.internic.net" but theres some odd things going on.



I updated the container to remove that check for the moment

Edited December 22, 20241 yr by Mainfrezzer

3 hours ago, Mainfrezzer said:

How are you running that container? Ipv6 only on br0 or something else?

I did include a test to check if the container is able to download the roothints and should only shutdown when it fails to ping "www.internic.net" but theres some odd things going on.



I updated the container to remove that check for the moment

 

no ipv6 here, just ipv4 from the br0 network

43 minutes ago, stayupthetree said:

 

no ipv6 here, just ipv4 from the br0 network

Odd. 

Does it work now without issue?

Hoping someone can help me.

 

Been trying to install Pelican Panel for the first time but it hangs on startup. Gets stuck at "Starting Supervisord"

 

Startup Logs are as follows;

mkdir: can't create directory '/pelican-data/database': File exists
external vars exist.
APP_KEY is already set.
Migrating Database

   INFO  Nothing to migrate.  

Optimizing Filament

   INFO  Caching components and Blade icons.  

  Caching components ............................................. 5.19ms DONE
  Caching Blade icons .......................................... 191.67ms DONE

Starting cron jobs.
Starting PHP-FPM and Caddy
Starting Supervisord

 

Have tried all the usual song and dance, different ports, network configs, new directories, privileged containers, and nothing I do gets past that initial startup procedure.

 

Any help would be greatly appreciated!

54 minutes ago, Nafers said:

Hoping someone can help me.

 

Been trying to install Pelican Panel for the first time but it hangs on startup. Gets stuck at "Starting Supervisord"

 

Startup Logs are as follows;

mkdir: can't create directory '/pelican-data/database': File exists
external vars exist.
APP_KEY is already set.
Migrating Database

   INFO  Nothing to migrate.  

Optimizing Filament

   INFO  Caching components and Blade icons.  

  Caching components ............................................. 5.19ms DONE
  Caching Blade icons .......................................... 191.67ms DONE

Starting cron jobs.
Starting PHP-FPM and Caddy
Starting Supervisord

 

Have tried all the usual song and dance, different ports, network configs, new directories, privileged containers, and nothing I do gets past that initial startup procedure.

 

Any help would be greatly appreciated!

thats usually all you get from that panel in terms of logs. 

If you kept the reverse proxy work around mapping (this one),

youre missing the Caddyfile that you need to create yourself as mentioned.

Edit:
Currently the default caddyfile that gets created takes in the value from this,

 

the issue with that arrises if you designate a https address, it causes a redirect loop behind a reverse proxy.


Edit Edit:

Im planning on creating the containers myself in a bit and that should remove a lot of the manual hassel you have to go through to get this all running

 

 

 

Edited December 24, 20241 yr by Mainfrezzer
added more info & formatting

Ive created a modified container and added template to CA, should be there at some point soon™️
It should be a lot more straight forward and require a lot less manual tinkering with the files.

The Panel container includes the modified Caddyfile by default, so reverse proxy is heavily recommended!

All you need to set on the panel template is the usual.

 

Then you access the panel, in my case https://panel.magnon.ovh/installer, if you want to install it locally first, change the address in the template to http://LANIP

 

 

after you finished installing, you have to add a node, which is the wing container.

 

The important thing apart from deciding if the Node is accessible via https or http is the port. The port tells the panel on what port it should check for the connection. If you put the wing behind a reverse proxy, always pick 443.


After you added the node, the panel will hand out a config.yml, which looks similar to this.

 

Here its important to have a look at the port. If you picked 443 for the reverse proxied node earlier, you would have to change the number back to 8080 or whichever mapping you picked on the Pelican-Wing container. Also, if you use a reverse proxy for the node, dont forget to set "SSL: enabled:" to false

The Data: point is set to fit the default template layout of the Mainfrezzer-Pelican-Wing template. You only need to change that if you chose to change the location i.e. you rather want it on a share instead of appdata.

 

They all have to match

 

 

 

Now is a good time to start the Pelican-Wing up once.

The Pelican-Wing container should complain that its missing the config file and you have to create a config.yml in the "/etc/pelican" location of the Pelican-Wing container, which is by default mapped to "/mnt/user/appdata/pelican-wing/etc/pelican"

 

Take note that you probably have to change the owner to nobody if you created that file via the cmd line, it would be owned by root.

 

 

After that, start the wing and you should see the following in the Webinterface of the Pelican-Panel

 

 

 

Edit:

A few things ive changed compared to the official container.

1. The default localtion its handing out, all to fit the mainfrezzer-pelican-**** templates and the UnRaid default.
2. Dockernetwork - The IP Ranges, it shouldnt collide with Pterodactyl created networks. Networkname is pelican_net with "172.19.99.0/24" and "fdba:17d8:6c94::/64"

Edited December 25, 20241 yr by Mainfrezzer
fixed wrong ip

Hi @Mainfrezzer, I've installed panel but got some error with wings.

INFO: [Dec 25 09:45:21.998] creating missing pelican0 interface, this could take a few seconds...
FATAL: [Dec 25 09:45:21.998] failed to configure docker environment error=Error response from daemon: invalid pool request: Pool overlaps with other one on this address space

 

I don't have Pterodactyl installed and no Pterodactyl network on my docker from previous installation (1 year ago). Do you have an idea how to bypass this problem since with your last version you added "Dockernetwork - The IP Ranges, it shouldnt collide with Pterodactyl created networks. Networkname is pelican_net with "172.18.99.0/24" and "fdba:17d8:6c94::/64""

1 hour ago, HuSoS said:

 

 

I don't have Pterodactyl installed and no Pterodactyl network on my docker from previous installation (1 year ago). Do you have an idea how to bypass this problem since with your last version you added "Dockernetwork - The IP Ranges, it shouldnt collide with Pterodactyl created networks. Networkname is pelican_net with "172.18.99.0/24" and "fdba:17d8:6c94::/64""

  

i pushed an update, i did goof. Should have been 172.19 not 172.18 🫣


Edit: you might have to check your config.yaml and change the ips in the list, in case it got populated already

Edited December 25, 20241 yr by Mainfrezzer
added picture

Good evening,

 

I really want to get pelican up an running. I cant seem to set it up for the life of me. i cant get pelcan panel and wing to run at the same time. Wing will close right away. Even with the config.yml looking at the log for wing the only thing to note is 

FATAL: [Dec 25 23:54:14.859] failed to configure docker environment error=Error response from daemon: Pool overlaps with other one on this address space

Stacktrace:
Error response from daemon: Pool overlaps with other one on this address space
 

 

 

 

i would gladly make a donation for help getting it running if thats aloud.

 

 

Edited December 26, 20241 yr by Keida

2 hours ago, Keida said:

 Even with the config.yml looking at the log for wing the only thing to note is 

FATAL: [Dec 25 23:54:14.859] failed to configure docker environment error=Error response from daemon: Pool overlaps with other one on this address space

Stacktrace:
Error response from daemon: Pool overlaps with other one on this address space

 

 

Whats your list of networks when you type "docker network ls" in the console?

to get things running asap, you can edit the config.yml and change the "network_mode:" from "pelican_nw" or "pelican_net" to "bridge", that would use the already existing default bridge network to run the container

Hello! does pelican work with cloudflare tunnel? I have followed every step and managed to get it up and running both containers but for some reason the pelican_net gets created with weird subnet interface like 10.16.5.0/24 instead of 172.18.0.0 and also when I remove the docker network and manually create it, the container still generates in the config.yml that same weird subnet interface.

57 minutes ago, Gorden said:

Hello! does pelican work with cloudflare tunnel? I have followed every step and managed to get it up and running both containers but for some reason the pelican_net gets created with weird subnet interface like 10.16.5.0/24 instead of 172.18.0.0 and also when I remove the docker network and manually create it, the container still generates in the config.yml that same weird subnet interface.

I would highly suspect that it does work with cloudflare tunnels, at least the https communication part.

 

The different subnet is normal, I changed it earlier to the 10.16.5.0/24 to make absolutely sure it won't interfere with any docker networks that could possibly exist. 

When I install your adguard-unbound container, it works well unless I try and install on br0 network.  Then the container seems to have no internet access, ie: can't ping google.com.

/opt/adguardhome/work # ping google.com
ping: bad address 'google.com'

Everything works fine on custom docker network but I would like it to have its own IP.

 

I have pihole unbound currently running on br0 with no issues but I can't figure out whats wrong in this case.

2 hours ago, bozzio said:

When I install your adguard-unbound container, it works well unless I try and install on br0 network.  Then the container seems to have no internet access, ie: can't ping google.com.

/opt/adguardhome/work # ping google.com
ping: bad address 'google.com'

Everything works fine on custom docker network but I would like it to have its own IP.

 

I have pihole unbound currently running on br0 with no issues but I can't figure out whats wrong in this case.

seems to be an issue with ping on alpine. i was able to recreate it, but curl does work fine.

 

 

 

after running apk update and apk upgrade, ping works again. Ill update the container in a bit

11 hours ago, Mainfrezzer said:

to get things running asap, you can edit the config.yml and change the "network_mode:" from "pelican_nw" or "pelican_net" to "bridge",

Thank you for your response, looking at the config.yml there doesnt seem to be a spot called netowrk mode or pelcan_nw or pelcan_net.