Crovaxon

Standardgemäß verlangt Collabora HTTPS auch im lokalen Netz, eventuell da was übersehen in der Konfiguration von SWAG? Ansonsten muss man je nachdem ob HTTP oder HTTPS eine entsprechende nginx config hinterlegen, siehe Doku von Collabora bezüglich nginx reverse proxy: https://sdk.collaboraonline.com/docs/installation/Proxy_settings.html

Können schon, wäre aber unwahrscheinlich, sonst hättest du sicherlich Beschwerden im Web darüber finden können. Hattest du den Archer C7 schon vorher oder kam der mit dem Anbieterwechsel? Ist einer von der simplen Sorte, die leiten nur strikt auf die eingetragene IP weiter so wie ich das vom Handbuch entnehme. Passt die hinterlegte IP in der Weiterleitung weiterhin zu der lokalen IP deines Servers? Wenn der seine IP via DHCP bezieht, solltest du über eine statische IP für deinen Server nachdenken damit diese sich eben nicht unerwartet mal ändern kann. Oder sofern der Router das anbietet, die durch DHCP vergebene Adresse dem Server fest zuweisen. Address Reservation sollte der Archer auch können, dann wird die IP an die MAC Adresse der Netzwerkkarte des Servers gebunden.

Statt oflag=direct sollte es wahrscheinlich iflag=direct heißen, oflag betrifft den output, iflag den input und es ist ja der input der nicht aus dem cache kommen soll, sondern direkt von der Festplatte.

Powertop (aber über Umwege die 2.14 natürlich) und iotop, außerdem Python 2.7, aber ich weiß beim besten willen nicht mehr für welches Plugin wenn überhaupt, keines meiner aktuell in Nutzung befindlichen haben eine angegebene Python Abhängigkeit, also hab ich es wieder runtergeworfen.

Klingt an sich tatsächlich sehr interessant als vorweg Filter für die eigenen öffentlichen Dienste, gerade wenn vollautomatisiert aus bestimmten Ländern ja öfters nach offenen Ports und dahinter liegenden angreifbaren Diensten gescannt wird, sowas lässt sich dann ja abfangen. Vorausgesetzt diese nutzen nicht einfach selber VPNs um genau solcher Filterung zu entkommen. Die Geo Infos cachen ist definitiv sinnvoll, aber ob man mehrere Monate IPs speichern sollte weiß ich jetzt nicht, durchaus haben unsere ISPs hier ja ihre schon seit Jahrzehnten abgeklopften Ranges die sie weiterhin nutzen, man kein bei der RIPE leider nicht eben mal eben so auf die Schnelle einsehen, wann zuletzt deutsche Registrare was neues zugewiesen bekommen haben, aber ich würde mich nicht wundern, wenn unsere ISPs sich weiterhin um jede freie IPv4 aus dem RIPE Pool bemühen, für die sich anstellen dürfen, ungenutzte IPs können ja wieder zurückgegeben und daher neu vergeben werden. Aber wie die Wirklichkeit aussieht weiß ich nicht. Außerdem kümmert sich die RIPE ja nicht um die Geo Informationen, so wie ich das verstehe, können die Registrare selbst freiwillig diese Info angeben und diese ganzen Geo Dienste verarbeiten das weiter bzw. laufen Neuregistrationen selbst hinterher um zu gucken wer das ist und woher die kommen. https://www.ripe.net/manage-ips-and-asns/db/tools/geolocation-in-the-ripe-database IP2Location z.B. updated ihre Datenbanken jeweils monatlich. https://www.ip2location.com/faqshttps://www.ip2location.com/faqs Ist ansonsten aber ein interessantes Projekt. 45 Anfragen pro Minute in deinem Beispiel klingen an sich ganz fair, sehr interessant wäre es jetzt wenn man jetzt noch im Reverse Proxy log nachguckt, wie häufig in der Minute bei ihm angeklopft wird.

Jup, außerdem, dank der Erfindung von "auto crossover", können Netzwerkgeräte die dies beherrschen selber bestimmen, auf welchen Adern des Ports Gesendet/Empfangen wird und zwischen sich und ihrem Gesprächspartner erkennen, ob crossover geschaltet werden muss oder nicht... und dieses Feature wurde schnell zur Selbstverständlichkeit, dann muss man sich nicht mehr Gedanken ums Kabel machen und alles was 1 GBit oder schneller spricht, braucht das sowieso nicht mehr wie DataCollector schon sagt. (1 Gbit ports, die aber zur Abwärtskompabilität runterschalten auf 100 oder 10 MBit verwenden auto crossover weiterhin zum Aushandeln und auch wenn das ein optionales Feature war, isses nicht weg zu denken und es ist ne Rarität, ein modernes Netzwerkgerät zu finden, das nicht dieses feature hat). Das letzte Mal wo ich über sowas gestolpert war, waren das die Uralt LANs mit meinen Brüdern und Freunden und wenn man sich die falschen Kabel aus Papas Netzwerkkiste geborgt hatte da kommt Nostalgie auf.

Ich erinnere mich dunkel daran, dass meine SATA HDDs auch recht selten CRC error SMART Fehler gemeldet hatten aber ich ansonsten nie Probleme im monatelangen Betrieb hatte. Aber das ist ne Weile her und hatte sich dann gänzlich gelegt, als ich das BIOS des Mainboards mal aktualisiert hatte, kann aber auch gut daran liegen, dass ich danach mich damit auseinander gesetzt habe, die Platten anständig schlafen zu schicken. Vorher waren meine cache SSD permanent aktiv und mein HDD array auch dauerhaft wach wegen Zugriffen von mitteilungsbedürftigen Docker Containern, die viel in ihre logs schrieben. Jetzt schlafen meine Platten fast durchweg.

Not every docker container writes excessively to a log file, not every person uses chatty docker containers so those people are naturally not confronted or have only an amount of writes that they do not care/worry about. And I assume there are also people that do not notice it at all. I too did not immediately notice that myself, everything was working after all and my SSD being active seemed logical to me the more containers I introduced to my system. Only on closer look I saw that the amount of write accesses seemed unexpectedly high while none of my containers were particularly much used or active.

With the recent update to CA I only had entries for apps that had updates and after installing those updates, Action Centre does not show up with anything unexpected

Array ( [0] => Array ( [Name] => dokuwiki [Registry] => https://registry.hub.docker.com/r/google/cadvisor/ [Repository] => google/cadvisor:latest [Environment] => Array ( [Variable] => Array ( [Name] => detach [Value] => true ) ) [Networking] => Array ( [Mode] => bridge [Publish] => Array ( [Port] => Array ( [HostPort] => 8081 [ContainerPort] => 8080 [Protocol] => tcp ) ) ) [Data] => Array ( [Volume] => Array ( [0] => Array ( [HostDir] => / [ContainerDir] => /rootfs [Mode] => ro ) [1] => Array ( [HostDir] => /var/run [ContainerDir] => /var/run [Mode] => rw ) [2] => Array ( [HostDir] => /sys [ContainerDir] => /sys [Mode] => ro ) [3] => Array ( [HostDir] => /var/lib/docker/ [ContainerDir] => /var/lib/docker/ [Mode] => ro ) ) ) [Icon] => https://i.imgur.com/stlnoKR.png [Repo] => smdion's Repository [Support] => http://lime-technology.com/forum/index.php?topic=34009.0 [TemplateURL] => https://raw.githubusercontent.com/smdion/docker-containers/templates/smdion-repo/cAdvisor.xml [ModeratorComment] => This dockerHub repository has been deprecated and will no longer receive any updates. You should uninstall and reinstall the container from SelfHosters which utilizes the correct and updated repository from Google [Deprecated] => 1 [Overview] => Dokuwiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki. [templatePath] => /tmp/GitHub/AppFeed/templates/smdionsRepository/smdion-repo/cAdvisor.xml [CategoryList] => Array ( [0] => Tools-Utilities ) [downloads] => 1624577423 [stars] => 449 [trending] => 0.116 [trends] => Array ( [0] => 0.884 [1] => 1.348 [2] => 1.531 [3] => 1.127 [4] => 1.202 [5] => 0.14 [6] => 0.116 ) [trendsDate] => Array ( [0] => 1635379402 [1] => 1637975020 [2] => 1640574233 [3] => 1643173393 [4] => 1645772606 [5] => 1648368210 [6] => 1650967418 ) [downloadtrend] => Array ( [0] => 1537653325 [1] => 1558664556 [2] => 1582900693 [3] => 1600940236 [4] => 1620423111 [5] => 1622687293 [6] => 1624577423 ) [LastUpdateScan] => 1650967418 [LastUpdate] => 1629082624 [FirstSeen] => 1 [topTrending] => -0.768 [topPerforming] => 0.116 [Category] => Tools:Utilities [ID] => 0 [Displayable] => 1 [Author] => google [DockerHubName] => cadvisor [RepoName] => smdion's Repository [SortAuthor] => google [SortName] => dokuwiki [random] => 1462868356 [Blacklist] => [MinVer] => 6.0 [Path] => /tmp/community.applications/tempFiles/templates-community-apps/smdionsRepository/google-cadvisor-latest.xml [trendDelta] => -0.768 [trendAverage] => 0.9069 [Compatible] => 1 [CardDescription] => Dokuwiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki. [InstallPath] => /boot/config/plugins/dockerMan/templates-user/my-dokuwiki.xml [NoPin] => 1 [Uninstall] => 1 ) [1] => Array ( [Name] => mariadbnextcloud [Registry] => https://registry.hub.docker.com/r/google/cadvisor/ [Repository] => google/cadvisor:latest [Environment] => Array ( [Variable] => Array ( [Name] => detach [Value] => true ) ) [Networking] => Array ( [Mode] => bridge [Publish] => Array ( [Port] => Array ( [HostPort] => 8081 [ContainerPort] => 8080 [Protocol] => tcp ) ) ) [Data] => Array ( [Volume] => Array ( [0] => Array ( [HostDir] => / [ContainerDir] => /rootfs [Mode] => ro ) [1] => Array ( [HostDir] => /var/run [ContainerDir] => /var/run [Mode] => rw ) [2] => Array ( [HostDir] => /sys [ContainerDir] => /sys [Mode] => ro ) [3] => Array ( [HostDir] => /var/lib/docker/ [ContainerDir] => /var/lib/docker/ [Mode] => ro ) ) ) [Icon] => https://i.imgur.com/stlnoKR.png [Repo] => smdion's Repository [Support] => http://lime-technology.com/forum/index.php?topic=34009.0 [TemplateURL] => https://raw.githubusercontent.com/smdion/docker-containers/templates/smdion-repo/cAdvisor.xml [ModeratorComment] => This dockerHub repository has been deprecated and will no longer receive any updates. You should uninstall and reinstall the container from SelfHosters which utilizes the correct and updated repository from Google [Deprecated] => 1 [Overview] => An Enhanced drop in replacement for Mysql [templatePath] => /tmp/GitHub/AppFeed/templates/smdionsRepository/smdion-repo/cAdvisor.xml [CategoryList] => Array ( [0] => Tools-Utilities ) [downloads] => 1624577423 [stars] => 449 [trending] => 0.116 [trends] => Array ( [0] => 0.884 [1] => 1.348 [2] => 1.531 [3] => 1.127 [4] => 1.202 [5] => 0.14 [6] => 0.116 ) [trendsDate] => Array ( [0] => 1635379402 [1] => 1637975020 [2] => 1640574233 [3] => 1643173393 [4] => 1645772606 [5] => 1648368210 [6] => 1650967418 ) [downloadtrend] => Array ( [0] => 1537653325 [1] => 1558664556 [2] => 1582900693 [3] => 1600940236 [4] => 1620423111 [5] => 1622687293 [6] => 1624577423 ) [LastUpdateScan] => 1650967418 [LastUpdate] => 1629082624 [FirstSeen] => 1 [topTrending] => -0.768 [topPerforming] => 0.116 [Category] => Tools:Utilities [ID] => 0 [Displayable] => 1 [Author] => google [DockerHubName] => cadvisor [RepoName] => smdion's Repository [SortAuthor] => google [SortName] => mariadbnextcloud [random] => 1462868356 [Blacklist] => [MinVer] => 6.0 [Path] => /tmp/community.applications/tempFiles/templates-community-apps/smdionsRepository/google-cadvisor-latest.xml [trendDelta] => -0.768 [trendAverage] => 0.9069 [Compatible] => 1 [CardDescription] => An Enhanced drop in replacement for Mysql [InstallPath] => /boot/config/plugins/dockerMan/templates-user/my-mariadbnextcloud.xml [NoPin] => 1 [Uninstall] => 1 ) [2] => Array ( [Name] => red-discordbot [Registry] => https://registry.hub.docker.com/r/google/cadvisor/ [Repository] => google/cadvisor:latest [Environment] => Array ( [Variable] => Array ( [Name] => detach [Value] => true ) ) [Networking] => Array ( [Mode] => bridge [Publish] => Array ( [Port] => Array ( [HostPort] => 8081 [ContainerPort] => 8080 [Protocol] => tcp ) ) ) [Data] => Array ( [Volume] => Array ( [0] => Array ( [HostDir] => / [ContainerDir] => /rootfs [Mode] => ro ) [1] => Array ( [HostDir] => /var/run [ContainerDir] => /var/run [Mode] => rw ) [2] => Array ( [HostDir] => /sys [ContainerDir] => /sys [Mode] => ro ) [3] => Array ( [HostDir] => /var/lib/docker/ [ContainerDir] => /var/lib/docker/ [Mode] => ro ) ) ) [Icon] => https://i.imgur.com/stlnoKR.png [Repo] => smdion's Repository [Support] => http://lime-technology.com/forum/index.php?topic=34009.0 [TemplateURL] => https://raw.githubusercontent.com/smdion/docker-containers/templates/smdion-repo/cAdvisor.xml [ModeratorComment] => This dockerHub repository has been deprecated and will no longer receive any updates. You should uninstall and reinstall the container from SelfHosters which utilizes the correct and updated repository from Google [Deprecated] => 1 [Overview] => The newest Red-Discordbot in a convenient multi-arch container How to create a bot account: https://discordpy.readthedocs.io/en/v1.0.1/discord.html#creating-a-bot-account Readme: https://github.com/PhasecoreX/docker-red-discordbot [templatePath] => /tmp/GitHub/AppFeed/templates/smdionsRepository/smdion-repo/cAdvisor.xml [CategoryList] => Array ( [0] => Tools-Utilities ) [downloads] => 1624577423 [stars] => 449 [trending] => 0.116 [trends] => Array ( [0] => 0.884 [1] => 1.348 [2] => 1.531 [3] => 1.127 [4] => 1.202 [5] => 0.14 [6] => 0.116 ) [trendsDate] => Array ( [0] => 1635379402 [1] => 1637975020 [2] => 1640574233 [3] => 1643173393 [4] => 1645772606 [5] => 1648368210 [6] => 1650967418 ) [downloadtrend] => Array ( [0] => 1537653325 [1] => 1558664556 [2] => 1582900693 [3] => 1600940236 [4] => 1620423111 [5] => 1622687293 [6] => 1624577423 ) [LastUpdateScan] => 1650967418 [LastUpdate] => 1629082624 [FirstSeen] => 1 [topTrending] => -0.768 [topPerforming] => 0.116 [Category] => Tools:Utilities [ID] => 0 [Displayable] => 1 [Author] => google [DockerHubName] => cadvisor [RepoName] => smdion's Repository [SortAuthor] => google [SortName] => red discordbot [random] => 1462868356 [Blacklist] => [MinVer] => 6.0 [Path] => /tmp/community.applications/tempFiles/templates-community-apps/smdionsRepository/google-cadvisor-latest.xml [trendDelta] => -0.768 [trendAverage] => 0.9069 [Compatible] => 1 [CardDescription] => The newest Red-Discordbot in a convenient multi-arch container How to create a bot account: https://discordpy.readthedocs.io/en/v1.0.1/discord.html#creating-a-bot-account Readme: https://github.com/PhasecoreX/docker-red-discordbot [InstallPath] => /boot/config/plugins/dockerMan/templates-user/my-red-discordbot.xml [NoPin] => 1 [Uninstall] => 1 ) )

It was still flagging after a force reload in the browser. Cleared cache and cookies and logged back in, the Action Centre still shows up with a warning sign, but clicking on it gives me a "No matching applications found" on the apps list and then boots me back to the Home screen, with the Action Centre now hidden. But everytime I switch tabs and return back to the Apps tab, it loads it with the Action Centre showing and blinking.

I did have another Collabora image installed previously (simply named Collabora) that complained for the same reason, it did have some problems recently that always required me to manually fix its container settings after an update, so I figured I might as well switch to the only other Collabora image CA showed me, Collabora-CODE. After disabling the old container, installing the new one based on the Collabora-CODE image and running it, I did try to remove the old container together with its image but it threw an error that the image was still in use and just removed the container, perhaps both images are based on the same docker image? Is that why it is marked for duplicated template? But all in all I had no trouble switching to Collabora-CODE, despite it now being shown as blacklisted as well in the Action Centre.

So about this new Action Centre... What exactly does it mean if an app is blacklisted? For example the Collabora-CODE image is set as blacklisted with the reason it being a "Duplicated Template". What does that mean?

Awesome, I had been wondering when somebody would put a docker image together for it. One question though, the rendering of the GUI is done by the host machine or am I wrong? It is a little choppy and tears when you move the windows inside it, so I wonder if hardware acceleration could be somehow brought into it? Not that it really needs it considering one is writing mostly just text in it, but I have a GPU in my Unraid machine and use it for Plex, can I have the image make use of it as well?

Es ist nicht hübsch und könnte definitiv ein responsive design gebrauchen, das stimmt. Ich konnte aber dennoch bisher alles über die Oberfläche erledigen, wenn nötig, muss dann nur notfalls den Bereich der Seite vergrößern mit dem ich interagiere, Stichwort zwei Finger pinch zoom.

I have switched to the extra parameters Variant of creating a ramdisk for my chatty and active containers, that works just as well for now. Finally understanding better how to take advantage of my added cache drive and how to help it not be bombarded as well, I finally managed to get my array disks to stay spun down. Now to keep a good eye on what is interacting how much with my cache drive on a daily basis and I'll hope to have my drive wear under good control soon.

Hello, I was looking into this to have the tmp folders of some of my dockers reside in RAM as well and it seemed a straightforward way to set up like this. Initially it also worked but I have had reasons to reboot my machine and then suddenly my nextcloud docker refused to start up as it was not able to write to its mapped tmp folder, the perms on the nextcloud folder in temp were set up for the user root. After some digging I also found this: Seems to not be encouraged to use the /tmp folder for something like this.