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:

github.com

rockstor/rockon-registry/blob/master/zoneminder.json#L39


                    "description": "Choose a Share for the database.",
                    "label": "MySQL Storage",
                    "min_size": "1073741824"
                }
            }
        }
    },
    "description": "ZoneMinder: Free, open-source software to control IP, USB and Analog (CCTV) cameras (v1.29) - please note this runs as privileged in docker (to set shm to a higher amount)",
    "more_info": "</h4>Tips and Setup Instructions:</h4></p>        </p>        This container includes mysql, no need for a separate mysql/mariadb container</p>            All settings and library files are stored outside of the container and they are preserved when this docker is updated or re-installed (change the variable /path/to/config in the run command to a location of your choice)</p>            This container includes avconv (ffmpeg variant) and cambozola but they need to be enabled in the settings. In the WebUI, click on Options in the top right corner and go to the Images tab</p>            Click on the box next to OPT_Cambozola to enable</p>            Click on the box next OPT_FFMPEG to enable ffmpeg</p>            Enter the following for ffmpeg path: /usr/bin/avconv</p>                Enter the following for ffmpeg output options: -r 30 -vcodec libx264 -threads 2 -b 2000k -minrate 800k -maxrate 5000k (you can change these options to your liking)</p>                    Next to ffmpeg_formats, add mp4 (you can also add a star after mp4 and remove the star after avi to make mp4 the default format)</p>                    Hit save</p>                    Now you should be able to add your cams and record in mp4 x264 format</p>                    Important:</p>                    </p>                    The web gui will be available at http://serverip:port/zm</p>                    On first start, open zoneminder settings, go to the paths tab and enter the following for PATH_ZMS: /zm/cgi-bin/nph-zms</p>                        The default timezone for php is set as America/New_York if you would like to change it, edit the php.ini in the config folder. Here's a list of available timezone options: http://php.net/manual/en/timezones.php",
    "ui": {
        "slug": "/zm"
    },
    "volume_add_support": true,
    "version": "1.0",
    "website": "https://github.com/aptalca/docker-zoneminder/tree/v1.29"
}
}

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

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

A [Docker](https://www.docker.com/what-docker) project to make lightweight x86 and ARM container with [pi-hole](https://pi-hole.net) functionality.  Why?  Originally designed to be a quick, easy, and portable way to run x86 Pi-Hole, it now has an arm specific tag too.

1) Install docker for your [x86-64 system](https://www.docker.com/community-edition) or [ARMv6l/ARMv7 system](https://www.raspberrypi.org/blog/docker-comes-to-raspberry-pi/) using those links.
2) Use the appropriate tag (x86 can use default tag, ARM users need to use the `arm` tag) in the below `docker run` command
3) Enjoy!

[![Build Status](https://api.travis-ci.org/diginc/docker-pi-hole.svg?branch=master)](https://travis-ci.org/diginc/docker-pi-hole) [![Docker Stars](https://img.shields.io/docker/stars/diginc/pi-hole.svg?maxAge=604800)](https://store.docker.com/community/images/diginc/pi-hole) [![Docker Pulls](https://img.shields.io/docker/pulls/diginc/pi-hole.svg?maxAge=604800)](https://store.docker.com/community/images/diginc/pi-hole)

[![Join the chat at https://gitter.im/diginc/docker-pi-hole](https://badges.gitter.im/diginc/docker-pi-hole.svg)](https://gitter.im/diginc/docker-pi-hole?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

## Running Pi-Hole Docker

[DockerCloud](https://store.docker.com/community/images/diginc/pi-hole) automatically builds the latest docker-pi-hole changes into images which can easily be pulled and ran with a simple `docker run` command.  Changes and updates under development or testing can be found on the [dev tags](#development)

One crucial thing to know before starting is this container needs port 53 and port 80, 2 very popular ports that may conflict with existing applications.  If you have no other services or dockers using port 53/80 (if you do, keep reading below for a reverse proxy example), the minimum arguments required to run this container are in the script [docker_run.sh](https://github.com/diginc/docker-pi-hole/blob/master/docker_run.sh) or summarized here:

```
IP_LOOKUP="$(ip route get 8.8.8.8 | awk '{ print $NF; exit }')"  # May not work for VPN / tun0
IPv6_LOOKUP="$(ip -6 route get 2001:4860:4860::8888 | awk '{ print $10; exit }')"  # May not work for VPN / tun0
IP="${IP:-$IP_LOOKUP}"  # use $IP, if set, otherwise IP_LOOKUP

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.