Posts by coffinbearer

Hi, based on your logs I'm assuming you are using a 32bit OS. This may be the reason for the service failing:

https://docs.linuxserver.io/fa…ges-based-on-ubuntu-focal

Linuxserver FAQ: My host is incompatible with images based on Ubuntu Focal and Alpine 3.13

- the switch to a image running bionic is only needed if you are using a 32bit OS host-is-incompatible-with-images-based-on-ubuntu-focal

- for updates check your version tag: linuxserver/plex Application Setup

You can also disable the "Allow media deletion" option in your Plex Server Library Settings

assuming your traefik instance is running with a ssl-certifacte from letsencrypt (for your Cloudflare DNS entry) and your ports 80 and 443 are open just enter your public ip-address in your web browser. You should receive an error message akin to the one in the attachment.

This would mean your traefik instance is running, receiving the connection and checking your ssl-certificate (which is failing because it is only valid for your dns entry and we tried to direct connect).

it looks like the dockerfile of cloudcmd had a missnamed entrypoint, thats the reasen the file (cloudcmd.js) could not found during startup.

Remove the image and pull a fresh one.

- can you access traefik via your public ip-adress, at least there should be a ssl error (if you have a certificate).

- you can try to activate the traefik acceslog to check if the connection actually reaches traefik.

- you can try to setup a basic container to use with traefik to rule a problem with your other services.

- did you update your traefik container? if so, have you checked the traefik v2 minor migration documentation.

Hi,

did you check the traefik dashboard if all your routers, services, etc. are functional.

You can check via your host-ip if you temporarily activate the insecure-dashboard.

Hi,

OP from your screenshot i'm asuming you are using the latest linuxserver/plex docker on your raspberry, if so this is broken due to the container base image being updated see: Upgrade to Ubuntu 20.04 (Focal) . You need to change your docker container tag see github issue.

ich hatte ähnliche Probleme einen smargo reader zum laufen zu bekommen. Für mich war die Lösung das Reader Protokoll in oscam auf "smargo" umzustellen und sicherzustellen das die Rechte der dialout gruppe und des abc users im Container korrekt [Referenz] sind. Ich nehme an der linuxserver-oscam container ist im Einsatz dann können die Berechtigungen wie folgt angepasst werden [Referenz - "Custom Scripts"].

Inhalt der Datei:

#!/bin/bash

echo "**** setting permissions for Card Reader ****"
groupmod -g 20 dialout
usermod -a -G dialout abc

Die Gruppen-ID ist gegebenenfalls an das eigene System anzupassen.

Yield79 as far as i understand the changelog omvextrasorg (5.3.2) adds a override config file to wait for the local filesystem to become available.

check if the file is there /etc/systemd/system/docker.service.d/waitLocalFs.conf

the github commit: https://github.com/OpenMediaVa…7e8397b40e0096d837db17cee

if your plex server is running as it is supposed to you can add libraries under the following menu: Settings > Manage > Libraries > Add Library

as long as you use portainer in single mode you should be aware of it's restrictions regarding stacks (compose files) : https://github.com/portainer/portainer/issues/3750

there are a few extra steps to activate the sharedfolders, but you should really reconsider it:

RE: Shared Folders not appearing in /sharedfolders/

ryecoaaron as far as i could gather from the op he installed omv on a i386 system and if i understood the omv-extras code correctly the status gets checked against the docker-ce ( docker status check ) but installs the docker.io package ( docker install )

yes the https redirection goes in your traefik.yml, but i didn't expect it to fix all our problems.

- did you remove the "metrics" section in your traefik.yml to reduce the error potential. (let's get a bare bones setup running)

- did you increase your traefik log level to DEBUG, if so post a log file.

Methy yes with traefik v2.2 a default entrypoint got added for it. traefik.docs and github commit

tinh_x7 as far as i can see you only changes schemes i'm talking about "HTTPS redirection (80 to 443)"

no it is not wrong but maybe unnecessary:

with the following yml block you activated the docker provider:

  docker:

an with

exposedByDefault: false

you told traefik to not automatically add all active docker containers.

if your emby and or plex services are docker containers you could add them via traefik labels like so (assuming you use a compose file):

(personally i would use labels if possible)

    labels:
        - "traefik.enable=true"
       # - "traefik.docker.network=proxy_web"
        - "traefik.http.routers.plex.rule=Host(`plex.abczyz.com`)"
        - "traefik.http.routers.plex.tls=true"
        - "traefik.http.routers.plex.tls.certresolver=le"
        - "traefik.http.routers.plex.entrypoints=https"
       # - "traefik.http.routers.plex.middlewares=logins@file"
        - "traefik.http.services.plex.loadbalancer.server.port=32400"

since you are using traefik v2.2 i would also add the newly added default redirectionfor http => https:

this goes in your static configuration

entryPoints:
  http:
    address: :80
    http:
      redirections:
        entryPoint:
          to: https
          scheme: https

  https:
    address: :443

you should also set you log level to DEBUG i may reveal some insight and remove the whole metrics block until your services work.

EDIT:

my bad to active the docker provider via static file config you need: docs.traefik.io

  docker:
  endpoint: "unix:///var/run/docker.sock"

both your servies point to "media.abcxyz.com" how should traefik know which one you want?

why did you activate the docker provider if your setup is provided from the file provider? ... or did you setup yout traefik via docker labels?

tinh_x7 i have no idea what you are doing... please show your traefik configs static and dynamic.

Edit: and your traefik log file during startup i would like to see how you got your certificate issued.