Got a few Services Running on Rockstor (Dropbox, Pi-hole, Plexrequests, etc)

KarstenV · May 8, 2017, 5:09pm

Here you go.

Strange that it wont work, everything seems to be working, its definately blocking ads as it should.

Fredrik · May 8, 2017, 5:12pm

Ah i think i might have spotted a problem
The IPv6 should be “true” or “false”
I use: false

Can you test to change that and see if it works better?

KarstenV · May 8, 2017, 5:16pm

OK, tried changing that setting:

Sadly does not seem to work:

coleberhorst · May 8, 2017, 5:19pm

What I have to do is go to http://ROCKSTOR_IP/#home and that bypasses pi-hole.

Though I haven’t tried this docker yet, still running installed directly on system. I’ll try it soon!

KarstenV · May 8, 2017, 5:21pm

Didn’t work here either, sadly. I get the exact same message.

Luckily everything else seems to work.

KarstenV · May 8, 2017, 5:24pm

Oh, I can access the /admin page…

Its only the /web that seems blocked.

Fredrik · May 8, 2017, 5:44pm

Rockstor uses https (port 443)
Cant you get in if you type that?

coleberhorst · May 8, 2017, 5:47pm

Oh forgot about https:/ my bookmark for rockstor has it https://192.168.1.121/#home

Flox · May 8, 2017, 8:53pm

Interesting how the link to access this Rock-on’s webUI points to “/web”… Does anyone know where this could originate from? I tried to look into the container’s github repo but I couldn’t find a helpful corresponding line of code.

coleberhorst · May 8, 2017, 11:42pm

Ok, tried it out and it works well. I would suggest changing the webui link to ROCKSTOR_IP:PORT/admin because as stated above the /web is blocked by default. Can this be achieved by changing the slug variable? I am not familiar with the intricacies of the rockon json format

phillxnet · May 9, 2017, 8:45am

@Flox and @coleberhorst

Yes the “/web” bit of the UI URL comes from the Rock-on’s json slug entry. Look to the zoneminder json for another example of where this is used:
https://github.com/rockstor/rockon-registry/blob/master/zoneminder.json#L39
and it’s associated web interface url visible in the following section of the docs:
http://rockstor.com/docs/docker-based-rock-ons/zoneminder.html#zoneminder-ui
in the ZoneMinder Rock-on write up.

In that example for a host named “jstor.lan” and user interface port 8086:

jstor.lan:8086/zm/

Hope that helps.

Flox · May 9, 2017, 1:51pm

Thanks a lot @phillxnet!
I (somehow) missed this section in the json file.

I still have an odd behavior regarding this link, however, Even though the link is correct (http://serverIP:port/admin, it fails to load the first time, and the browser automatically tries to open serverIP/admin. Upon manually typing serverIP:port/admin, however, I can access the webUI without any problem.
I get this when using both Firefox and Chrome.

It’s just a minor issue, but I was curious as to why this happens…

Thanks again!

Fredrik · May 10, 2017, 10:04am

Thanks!
I changed the .json file

glenngould · May 10, 2017, 11:53am

@Fredrik I’ve also installed pi-hole, seems to work (at least I get the webUI running)
Is there any reason why your json-file is built on a rather old version of pi-hole?

WebUI shows the following message…version 3.X is available…

thanks

Fredrik · May 10, 2017, 12:14pm

Hello Roland,
The json-file does not contain the docker image.
It will download the latest docker image available.

Docker image is coming from this: https://hub.docker.com/r/diginc/pi-hole/
Tag: alpine / latest
As far as i know this is the most used docker source for pi-hole.

glenngould · May 10, 2017, 12:37pm

OK, the WebUi points to…for comparing the versions…there it says 3.0.1 is the lastest

Flox · May 10, 2017, 1:39pm

I wondered the same thing as you, and when looking at the container’s github, v2.13.2 is clearly specified.

github.com

diginc/docker-pi-hole/blob/master/install.sh#L3


#!/bin/bash -ex
mkdir -p /etc/pihole/
export CORE_TAG='v3.2.1'
export WEB_TAG='v3.2.1'
export FTL_TAG='2.13.1'
export USE_DEVELOPMENT_BRANCHES=false


#     Make pihole scripts fail searching for `systemctl`,
# which fails pretty miserably in docker compared to `service`
# For more info see docker/docker issue #7459
mv "$(which systemctl)" /bin/no_systemctl && \
# debconf-apt-progress seems to hang so get rid of it too
mv "$(which debconf-apt-progress)" /bin/no_debconf-apt-progress

It seems the upgrade to 3.0 is coming very soon, though:

Fredrik · July 24, 2017, 8:19pm

The docker image was updated a while back so anyone who installs now get a 3.x version

KarstenV · July 24, 2017, 11:50pm

@Fredrik

I have been using pi-hole ever since I first installed it.

But mine still reads:

I have tried stopping / starting the rockon. Uninstalling, downloading the json file again, and then reinstalling, but end up with the same older version.

What do I do to update?

Flox · July 25, 2017, 1:17am

I haven’t tried myself, but the container’s documentation reads:

If you try to use pihole’s built in updater it is not guaranteed to work; it almost assuredly won’t work for alpine but debian may. The preferred ‘docker way’ to upgrade is:

Download the latest version of the image: docker pull diginc/pi-hole
Throw away your container: docker rm -f pihole
Warning When removing your pihole container you may be stuck without DNS until step 3 - docker pull before you docker rm -f to avoid DNS inturruption OR always have a fallback DNS server configured in DHCP to avoid this problem all together.
If you care about your data (logs/customizations), make sure you have it volume mapped or it will be deleted in this step

github.com

pi-hole/docker-pi-hole/blob/master/README.md#upgrading

# Docker Pi-hole

<p align="center">
<a href="https://pi-hole.net"><img src="https://pi-hole.github.io/graphics/Vortex/Vortex_with_text.png" width="150" height="255" alt="Pi-hole"></a><br/>
</p>
<!-- Delete above HTML and insert markdown for dockerhub : ![Pi-hole](https://pi-hole.github.io/graphics/Vortex/Vortex_with_text.png) -->

## Upgrade Notes

- **Using Watchtower? See the [Note on Watchtower](#note-on-watchtower) at the bottom of this readme**

- As of `2023.01`, if you have any modifications for lighttpd via an `external.conf` file, this file now needs to be mapped into `/etc/lighttpd/conf-enabled/whateverfile.conf` instead

- Due to [a known issue with Docker and libseccomp <2.5](https://github.com/moby/moby/issues/40734), you may run into issues running `2022.04` and later on host systems with an older version of `libseccomp2` ([Such as Debian/Raspbian buster or Ubuntu 20.04](https://pkgs.org/download/libseccomp2), and maybe [CentOS 7](https://pkgs.org/download/libseccomp)).

  The first recommendation is to upgrade your host OS, which will include a more up to date (and fixed) version of `libseccomp`.

  _If you absolutely cannot do this, some users [have reported](https://github.com/pi-hole/docker-pi-hole/issues/1042#issuecomment-1086728157) success in updating `libseccomp2` via backports on debian, or similar via updates on Ubuntu. You can try this workaround at your own risk_  (Note, you may also find that you need the latest `docker.io` (more details [here](https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/))

- Some users [have reported issues](https://github.com/pi-hole/docker-pi-hole/issues/963#issuecomment-1095602502) with using the `--privileged` flag on `2022.04` and above. TL;DR, don't use that mode, and be [explicit with the permitted caps](https://github.com/pi-hole/docker-pi-hole#note-on-capabilities) (if needed) instead

This file has been truncated. show original

I would try stopping the rocking, then docker rm -f pihole after making sure you have a second DNS setup, before finally turning the rock-on back on. As far as I understand, it should pull the newer image then.

Again, I haven’t tried it myself so I’m mostly supposing.

Hope it helps.