[[Support] for atribe's repo Docker images]

9 minutes ago, Altair said:

 

I tried that on telegraf 1.4.3 but I'll only get

/bin/sh: 1: apk: not found

Do you know why?
Or what I can do to get apk to run?

 

Thank you!

 

Okay I managed to fix the error.

 

I had to set the repository to telegraf:1.4.3-alpine not telegraf:1.4.3 as it was before

[[Support] for atribe's repo Docker images]

23 hours ago, sureguy said:

docker exec -ti telegraf /bin/sh

 

apk add lm_sensors

 

I tried that on telegraf 1.4.3 but I'll only get

/bin/sh: 1: apk: not found

Do you know why?
Or what I can do to get apk to run?

 

Thank you!

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

4 hours ago, aptalca said:

 

Then it's your site config. Without seeing that, we have no idea

 

I found the problem.

I was working outside today and realized, that everything works fine from outside my LAN.

Turns out, my router ignores the port mapping I've created to map 80 from outside to 84 for let'sencrypt (as 80 is the Unraid GUI).

 

Probably going to change the gui port to 8080 so everything works fine even inside my LAN

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

1 minute ago, aptalca said:

 

Could be your site config for nextcloud or could be browser cache. 301 is a permanent redirect.

 

I tried opening the page via the by then untouched IE and still get the same result, e.g. http://subd.example.com/ will redirect me to the Unraid login dialog.

 

It does not only happen when trying to access my cloud but also whenever I try to open e.g. http://plex.example.com for Plex.

Thus, I conduct that it has to do something with letsencrypt.

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

Hello,

 

I've got the letsencrypt docker running, as well as some other dockers (mostly Nextcloud and Plex).

 

I tried to redirect all http-requests to https using a site-config-file as shown below:

 

server {
	listen 80;
	server_name *.example.com example.com;
	return 301 https://$host$request_uri;
}

The site-configs for Nextcloud etc. are in separate files and the default site-config-file is just an empty file.

 

Whenever I try to access my Cloud via https://cloud.example.com (note the https), everything is working fine.

But, whenever I try to access my Cloud via http://cloud.example.com, no redirect takes place and I am promted to enter my Unraid username and password (like root and password).

 

Does anyone have an idea what could be the reason for that?

[Request: Homebridge]

On 7.7.2017 at 9:03 AM, jrdnlc said:

 

docker exec -it homebridge bash is not working for me

 

root@unRAID:~# docker exec -t homebridge bash 
bash: docker: command not found

EDIT: I got it to work. The correct command is

 

docker exec -it Homebridge /bin/bash

 

 

You could simply run
 

docker exec homebridge sudo npm update -g homebridge

 

[[Support] for atribe's repo Docker images]

Okay,

 

I tried to set everything up, but I am complete newbie to UnRaid and dockers (and linux).

 

All I want for now is for Grafana to somehow get the current (and past) data from Glances and display it.

 

I installed grafana, influxdb and glances.

Grafana I running and I imported the json from https://github.com/nicolargo/glances/blob/master/conf/glances-grafana.json.

 

I also managed to activate the InfluxDB admin web interface and created multiple DBs.

 

The next step was installing Glances and running it with

--export-influxdb

.

 

Since then, Glances is somehow failing to start. See log:

 

Traceback (most recent call last):

File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main

"__main__", fname, loader, pkg_name)

File "/usr/lib/python2.7/runpy.py", line 72, in _run_code

exec code in run_globals

File "/glances/glances/__main__.py", line 29, in <module>

glances.main()

File "glances/__init__.py", line 225, in main

start_standalone(config=config, args=args)

File "glances/__init__.py", line 105, in start_standalone

standalone = GlancesStandalone(config=config, args=args)

File "glances/standalone.py", line 80, in __init__

self.screen = GlancesCursesStandalone(config=config, args=args)

File "glances/outputs/glances_curses.py", line 101, in __init__

self.screen = curses.initscr()

File "/usr/lib/python2.7/curses/__init__.py", line 33, in initscr

fd=_sys.__stdout__.fileno())

_curses.error: setupterm: could not find terminal

 

Traceback (most recent call last):

File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main

"__main__", fname, loader, pkg_name)

File "/usr/lib/python2.7/runpy.py", line 72, in _run_code

exec code in run_globals

File "/glances/glances/__main__.py", line 29, in <module>

glances.main()

File "glances/__init__.py", line 225, in main

start_standalone(config=config, args=args)

File "glances/__init__.py", line 105, in start_standalone

standalone = GlancesStandalone(config=config, args=args)

File "glances/standalone.py", line 80, in __init__

self.screen = GlancesCursesStandalone(config=config, args=args)

File "glances/outputs/glances_curses.py", line 101, in __init__

self.screen = curses.initscr()

File "/usr/lib/python2.7/curses/__init__.py", line 33, in initscr

fd=_sys.__stdout__.fileno())

_curses.error: setupterm: could not find terminal

 

I then tried to at least include the DB from InfluxDB in Grafana which is giving me an error I don't quite understand or with what I have no idea what to do now.

(See attached .png)

 

I would apprechiate any help