[Support] Organzir Organizr

[tronyx]

Just now, stFfn said:

why would i use organizr.domain.com?

of course im using my own domain.. where did you see that i use organizr.domain.com?

 

the swag and organizr dockers are up to date.

 

i dont know how anything else with nginx could interfere? port 443 is redirected to swag. how could anything else be taking over only this docker but not the others that im running?

We didn't see it, but Rox asked you because people have done that before and, since nothing is standing out as obvious to us as to what the issue could be, we're asking everything we can think of.

 

Either your containers are not up to date or you have another Nginx instance running either in another container or installed natively on the System that is running Docker.

 

root@suladan:~# docker exec -it organizr nginx -v
nginx version: nginx/1.20.1
root@suladan:~# docker exec -it swag nginx -v
nginx version: nginx/1.20.1

 

[stFfn]

5 minutes ago, Roxedus said:

Because the config you posted expose it on organizr.domain.com, not domain.com. That's why I asked, and waited for a answer

To clarify, domain.com in this context is supposed to be substituted with your real domain

where do you see the domain.com?

could you please pinpoint it to me? 

 

i see organizr.* in the config.

[tronyx]

1 minute ago, stFfn said:

where do you see the domain.com?

could you please pinpoint it to me? 

 

i see organizr.* in the config.

 

*sigh* We don't see it anywhere. Rox was simply making sure you were, in fact, browsing to organizr.domain.com and not just domain.com. Just a measure of validation, that's all.

[stFfn]

4 minutes ago, tronyx said:

 

*sigh* We don't see it anywhere. Rox was simply making sure you were, in fact, browsing to organizr.domain.com and not just domain.com. Just a measure of validation, that's all.

ohhhhh. i missunderstood. i thought you meant i am actually using organizer.DOMAIN.com.... and not my own domain

 

organizer is up to date.

 

swag is almost up to date. im staying on that version because i had issues with a later version.

 

and these are all my docker container

 

 

and i dont think unraid has a nginx installed nativly that interferes with only one docker.

 

do you thing its the swag version that is causing the problem?

 

 

 

Edited July 21, 2021 by stFfn

[HalianElf]

Version of SWAG is not the issue but I'm not sure why you have it pinned to a specific version instead of latest. That narrows it down to being your SWAG container though and you'll need to check the nginx error log in that and figure out why it's throwing the 500

[stFfn]

1 hour ago, HalianElf said:

Version of SWAG is not the issue but I'm not sure why you have it pinned to a specific version instead of latest. That narrows it down to being your SWAG container though and you'll need to check the nginx error log in that and figure out why it's throwing the 500

because i had an issue with a later version of it.. (cant remember what it was)

 

i didnt know there are error logs of nginx ^^

 

2021/07/21 23:25:21 [error] 679#679: *1235 auth request unexpected status: 404 while sending to client, client: 162.158.92.159, server: organizr.*, request: "GET /favicon.ico HTTP/1.1", host: "organizr.mydomain.de", referrer: "https://organizr.mydomain.de/"

 

but im not really sure what this means 😕

Edited July 21, 2021 by stFfn

[HalianElf]

2 minutes ago, stFfn said:

but im not really sure what this means 😕

That you put some kind of auth in front of it and whatever url it's trying to use is wrong and throwing a 404. You only showed the very top portion of the nginx config so can't help further than that with what you've provided so far.

[stFfn]

1 minute ago, HalianElf said:

That you put some kind of auth in front of it and whatever url it's trying to use is wrong and throwing a 404. You only showed the very top portion of the nginx config so can't help further than that with what you've provided so far.

 

## Version 2021/05/18
# make sure that your dns has a cname set for organizr

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name organizr.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    # enable for Authelia
    #include /config/nginx/authelia-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /ldaplogin;

        # enable for Authelia
        #include /config/nginx/authelia-location.conf;

        auth_request /auth-0;
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app organizr;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }

    # Optional redirect server errors to organizr error pages
    #error_page 400 402 403 404 405 408 500 502 503 504  $scheme://$host/?error=$status;

}

 

[HalianElf]

You can't auth organizr with itself. Remove the auth_request /auth-0;

[stFfn]

1 minute ago, HalianElf said:

You can't auth organizr with itself. Remove the auth_request /auth-0;

thx. that was the problem

 

[Puregreen59]

hi guys, wondering if anyone could Confirm if this is normal or not,

 

i have 14 tabs now, of which I have all 14 of them pinging, but with it set at 10 second updates or lower it causes the CPU to peg out under the SHFS process under top.

 

I've set this to 1 minute now because at one point caused a unresponsive server, I mean I know there's a few, but I would expect this type of behaviour from a couple of hundred but perhaps this is just normal? 

 

some side notes, I can get it to stop pegging out the CPU when I close Organizr under my browser, so I'm assuming it just doesn't send pings while no ones on the page which makes a bit of sense as there's no point really,

 

[CyberPunkMind]

Hi Guys,

Any one configured Organizrv2 to work with SSL Certificate?

I am using swag docker and want the SSL Certificate that swag creates to also be used in all my other applications (I am not talking about SSL Offloading with the swag reverse proxy, but actually have organizr listen on custom ssl port for example 8443 and use ssl certificate).

I didn't find any documentation on that in the official Orgnanizr docs.

 

[Update]

I tried to configure ssl.conf file in my appdata/organizr with the location of swag certificate, and add the line "include /cert_location/ssl.conf;" to the default site in organizr, sadly it did not work getting "ERR_SSL_PROTOCOL_ERROR"

(this worked with authelia)

Also, I am not sure if the change (if it will work) will be reverted with container update?

Edited September 19, 2021 by CyberPunkMind

[CyberPunkMind]

On 5/6/2021 at 2:18 PM, ados said:

The main issue with that application is support which has decreased over time.

You need to stay on older versions if you wish to have plugin support.

Keeping it short as this belongs over on the Deluge forum, you need to be on a 2.0.X version. 2.0.4 is a good one. 😉

Hi,

 

I got it working a while ago, I don't remeber exactly how, but I think it was because the latest python version binhex-delugevpn uses was 3.8, and you need to compile an egg "WebAPI-0.4.0-py3.8.egg'" with that version specifically

A good google searching will find you the answers, Sadly I did not save the guide a found back then, however now I found github issue on this with the solution and a link to an already compiled 3.8 egg

https://github.com/idlesign/deluge-webapi/issues/27

 

Good luck.

[mkono87]

I recently moved and using another subnet. Today I noticed with Org, that when I sign using Plex oAuth, while it is sucessful, I get a API connection failed and wont let me in. Plex is the only means I have to sign in atm. My nginx error log shows this. Any idea how I can fix this?

2021/09/27 09:12:08 [error] 381#381: *3408 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.18.0.2, server: _, request: "POST /api/v2/login HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7-fpm.sock", host: "main.mydomain.com", referrer: "https://main.mydomain.com/"

2021/09/27 09:12:08 [error] 381#381: *3408 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.18.0.2, server: _, request: "POST /api/v2/login HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7-fpm.sock", host: "main.mydomain.com", referrer: "https://main.mydomain.com/"

 

Edited September 27, 2021 by mkono87

[hermy65]

Any chance anyone can help me with some samesite/sameorigin issues im having with swag+organizr?

 

I was able to use the chrome flags when they were available to get things working, then they removed the flags so i resorted to a registry tweak but that no longer works for me either. I would like to get this fixed once and for all so i can continue to use things.

 

Right now i have everything going through swag using a name.domain.com format. If i use local ips for organizr + the organizr tabs use local ips i get the attached image when i inspect the tab. If i go through my reverse proxy with organizr.domain.com and all the tabs using service.domain.com i get the same thing. How do i resolve this once and for all?

 

 

[ados]

On 4/20/2021 at 10:27 PM, ados said:

Just want to thank the developers for Organizr its made management of services so much easier.

I would like to share a procedure for new peeps to secure their systems when using a reverse proxy, in this case NGINX Proxy Manager.

 

 

The following I think is a typical new proxy setup:

https://domain.com

Then the docker apps are setup either as subdomains https://sub.domain.com or sub-folders https://domain.com/subfolder

In both these instances the docker is exposed to the internet for hacking (we are dismissing firewalls in this example)

You can use Organizr to collaborate them together but its still the same.

https://organizr.com might be the location to access all the apps but https://sub.domain.com or sub-folders https://domain.com/subfolder is still there providing the address is used directly.

This is where we can use Organizr API to lock down the access to the sub domains and sub-folders.

 

When I access https://sub.domain.com or sub-folders https://domain.com/subfolder I get this:

 

This is because in this session I'm not logged into Organizr and so there is no authentication session to authorise me. If I did this in a browser I was logged into Organizr it would take me directly to the app but I could always go through Organizr too; thus I can do both but the public cannot.

Add this with SSO and even MFA for Organizr and we now have a secure login wall.

 

The following procedure explains how to do this for the easier NGINX app NGINX Proxy Manager (GUI based):

First you will need to have configured your NGINX PM docker, this is outside the scope of this guide so please review relevant procedures on their support forum; you will also need a configured Organizr using sub domains or sub-folders.

 

Sub-folder setup:

This setup is easier to configure and reduces complexity on domains/wildcards and SSL

 

1. In NGINX PM, edit the host relating to your Organizr which should have Organizr set on the "Details" screen and not a sub-folder; this ensures Organizr works effectively.

 

2. You have two options to configure the access:

Enter the following (with your own edit using examples below) auth_request /auth-4; into the "Advanced" tab if you want a global group block for all sub-folders.

OR

Enter the following (with your own edit using examples below) auth_request /auth-4; into the the custom configuration field (cog icon) for each sub-folder you want to restrict. This method allows for granularity. 

**Remember the restriction you place also applies to the user accessing the resources from within Organizr.

 

Replace the 4 with the match group level required to access the resource:

0=Admin
1=Co-Admin
2=Super User
3=Power User
4=User

Logged In Users=998
Guests=999

 

3. Create a new location which will contain the API call to Organizr for this to work:

Location: ~ /auth-(.*)

Scheme: http

Forward Hostname: 0.0.0.0/api/v2/auth?group=$1

Forward Port: 8040

 

**Replace the IP address values to your docker running Organizr and if you changed your default port also adjust that.

 

In the custom configuration field (cog icon) for that same location enter the following without edits:

 

internal;
proxy_set_header Content-Length "";

 

I have found this no longer works for newer NGINX versions breaking everything!

It seems the underlying config code has change which causes the 500 error.
I cannot verify what version the issue started, but if you are on version v2.9.11 you need to do this:

 

Edit the proxy host, select the far right advance tab and enter the following:

 

  location ~ /auth-(.*) {
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_pass       http://0.0.0.0:8999/api/v2/auth?group=$1;
    internal;
    proxy_set_header Content-Length "";
  }

 

**Replace the IP address values to your docker running Organizr and if you changed your default port also adjust that.

 

4. [Optional] if you have your Organizr connected to dockers using API (homepage items) via the proxy (don't know why you would, instead of local IP) then you will need to exclude the API call from needing authentication. For each location pointing to a docker using API in this configuration enter the following in the custom config (cog icon):

 

Example:

 

location /tautulli/api {
        auth_request off;
        proxy_pass http://0.0.0.0:8181/tautulli/api;
        }

 

**You might also have the auth_request /auth-4 text in there too which is fine. Replace the IP and port to your docker, replacing also the app names.

 

5. If you save it here you will block all users from accessing Organizr. This is because you need to be logged into Organizr to access Organizr, catch 22.

We fix this with one final location:

 

Location: /

Scheme: http

Forward Hostname / IP: 0.0.0.0

Forward Port: 8040

 

**Replace the IP address values to your docker running Organizr and if you changed your default port also adjust that.

 

In the custom configuration field (cog icon) for that same location enter the following without edits:

 

auth_request off;

 

This means when we go to https://domain.com it will automatically append a "/" to the end and the location bypasses the need to authenticate so we can login.

 

6. Setup complete

 

 

Sub-domain setup:

This is similar but with more repeating steps.

 

1. In NGINX PM, edit the host relating to your sub domain you want to restrict.

 

2. Enter the following (with your own edit using examples below) auth_request /auth-4; into the "Advanced" tab.
 

**Remember the restriction you place also applies to the user accessing the resources from within Organizr.

 

Replace the 4 with the match group level required to access the resource:

0=Admin
1=Co-Admin
2=Super User
3=Power User
4=User

Logged In Users=998
Guests=999

 

3. Create a new location which will contain the API call to Organizr for this to work:

Location: ~ /auth-(.*)

Scheme: http

 

Forward Hostname: 0.0.0.0/api/v2/auth?group=$1

Forward Port: 8040

 

**Replace the IP address values to your docker.

 

In the custom configuration field (cog icon) for that same location enter the following without edits:

 

proxy_pass_request_body off;

proxy_set_header Content-Length "";

 

I have found this no longer works for newer NGINX versions breaking everything!

It seems the underlying config code has change which causes the 500 error.
I cannot verify what version the issue started, but if you are on version v2.9.11 you need to do this:

 

Edit the proxy host, select the far right advance tab and enter the following:

 

  location ~ /auth-(.*) {
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_pass       http://0.0.0.0:8999/api/v2/auth?group=$1;
    internal;
    proxy_set_header Content-Length "";
  }

 

**Replace the IP address values to your docker running Organizr and if you changed your default port also adjust that.

 

4. [Optional] if you have your Organizr connected to dockers using API (homepage items) via the proxy (don't know why you would, instead of local IP) then you will need to exclude the API call from needing authentication. Click the "Advanced" settings tab and enter the following:

 

Example:

 

location /tautulli/api {
        auth_request off;
        proxy_pass http://0.0.0.0:8181/tautulli/api;
        }

 

**Replace the IP and port to your docker, replacing also the app names.

 

5. Repeat steps 1-4 for each sub domain.

 

6. Setup complete

 

I have updated the guide to remove many errors, sorry. 🙁

I have also found a compatibility issue with new versions of NGINX Manager.

Through comparing differences in previous backups to new versions I have resolved the issue and added to the guide.

Edited November 20, 2021 by ados
Spelling mistake

[elcapitano]

Cant get reverse proxy to work for organizr.

 

I am sorry having to ask for help on this, but I am at a loss.

 

Prereq: 

1) CNAME subdomain: "organizr.domain.xxx" has been created at cloudlare

2) Using SWAG - organizr.subdomain.conf has been configured (see attached)

3) SWAG restarted

4) Organizr is on docker's proxynet

5) Container name is "organizr"

 

What am I missing?

 

Container is up and running locally. .. 

 

Edited May 10, 2022 by elcapitano

[Roxedus]

Cant get reverse proxy to work for organizr.
 
I am sorry having to ask for help on this, but I am at a loss.
 
Prereq: 
1) CNAME subdomain: "organizr.domain.xxx" has been created at cloudlare
2) Using SWAG - organizr.subdomain.conf has been configured (see attached)
3) SWAG restarted
4) Organizr is on docker's proxynet
5) Container name is "organizr"
 
What am I missing?
 
Container is up and running locally. .. 
 

Upstream_port is 80

[elcapitano]

4 hours ago, Roxedus said:

Upstream_port is 80

😱 Thanx - that was it

[neutraltone]

Hi There,

 

EDIT: Since I started the post I've been reading up and digging further into this, I think there might be a disk issue and have added more details to the bottom of the message. Please let me know if there's a more appropriate place to post this question now since I've norrowed down the issue a bit.

Still fairly new to Unraid and Docker so please let me know if you need more information.

 

I was running into some issues accessing Organizr in the browser local when setting the port to `280`. It appears from looking at the logs that there was a lot of errors regarding the `/vendor` directory having `No data available` so the app couldn't boot due to not being able to find composer dependencies (I think). Here are the logs for the `organizrv2` container:
 

mv: cannot stat '/config/nginx/site-confs/default': No such file or directory
chown: cannot read directory '/config/www/organizr/api/vendor': No data available
chmod: cannot read directory '/config/www/organizr/api/vendor': No data available
fatal: destination path '/config/www/organizr' already exists and is not an empty directory.
chown: cannot read directory '/config/www/organizr/api/vendor': No data available
chmod: cannot read directory '/config/www/organizr/api/vendor': No data available
fatal: destination path '/config/www/organizr' already exists and is not an empty directory.
chown: cannot read directory '/config/www/organizr/api/vendor': No data available
chmod: cannot read directory '/config/www/organizr/api/vendor': No data available
fatal: destination path '/config/www/organizr' already exists and is not an empty directory.
--------------------------------------
|      Copying default site file     |
--------------------------------------
[cont-init.d] 30-setup: exited 0.
[cont-init.d] 40-install: executing... 
-----------------------
| Installing Organizr |
-----------------------
[cont-init.d] 40-install: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing... 
usermod: no changes
-------------------------------------
GID/UID
-------------------------------------
User uid:    99
User gid:    100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-setup: executing... 
--------------------------------------
|      Backing up default file       |
--------------------------------------
--------------------------------------
|      Copying default site file     |
--------------------------------------
[cont-init.d] 30-setup: exited 0.
[cont-init.d] 40-install: executing... 
-----------------------
| Installing Organizr |
-----------------------
[cont-init.d] 40-install: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing... 
usermod: no changes
-------------------------------------
GID/UID
-------------------------------------
User uid:    99
User gid:    100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-setup: executing... 
[cont-init.d] 30-setup: exited 0.
[cont-init.d] 40-install: executing... 
-----------------------
| Installing Organizr |
-----------------------
[cont-init.d] 40-install: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
** Press ANY KEY to close this window ** 

 

Upon removal of the Docker container I check my `appdata` directory but `organizrv2` directory appeared to still be there. 

 

I checked through and basically everything is gone except a chain of empty folders. When I try to delete it I get the following error:
 

root@unraid:/mnt/user/appdata#: rm -rf organizrv2/
rm: cannot remove 'organizrv2/www/organizr/api/vendor': Directory not empty

 

So I navigate through to that direction and try listing what's inside of it:
 

root@unraid:/mnt/user/appdata/organizrv2/www/organizr/api/vendor# ls -lah
/bin/ls: reading directory '.': No data available total 0

 

I've tried giving myself full permissions, changing ownership and deleting with `sudo` only to get the same error. I had a feeling maybe that composer's vendor directory might be mounted somewhere but I have no idea what or where that might be. Also, `umount` tells me that the `vendor` directory isn't mounted:

 

root@unraid:/mnt/user/appdata# umount organizrv2/www/organizr/api/vendor/
umount: organizrv2/www/organizr/api/vendor/: not mounted.

 

Little unsure where to go from here so any suggestions would be greatly appreciated. Thanks!

 

EDIT:

I just checked the Unraid logs (probably should have started there). When I try to delete the `organizrv2` directory with `rm -rf` inside my `appdata` share the following is being displayed in the logs:
 

Sep 18 16:06:10 unraid kernel: blk_update_request: critical medium error, dev nvme0n1, sector 272000 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Sep 18 16:06:10 unraid kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_imap_to_bp+0x4e/0x6a [xfs]" at daddr 0x41e80 len 32 error 61
Sep 18 16:06:10 unraid kernel: blk_update_request: critical medium error, dev nvme0n1, sector 272000 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Sep 18 16:06:10 unraid kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_imap_to_bp+0x4e/0x6a [xfs]" at daddr 0x41e80 len 32 error 61

The following is the results from a smart scan on the drive
 

root@unraid:~# smartctl -a /dev/nvme0n1p1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.46-Unraid] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 970 EVO Plus 1TB
Serial Number:                      S6P7NG0R712023M
Firmware Version:                   3B2QEXM7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            85,334,732,800 [85.3 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 5711502ef7
Local Time is:                      Sun Sep 18 16:43:13 2022 BST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     7.54W       -        -    0  0  0  0        0       0
 1 +     7.54W       -        -    1  1  1  1        0     200
 2 +     7.54W       -        -    2  2  2  2        0    1000
 3 -   0.0500W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        36 Celsius
Available Spare:                    96%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    1,858,641 [951 GB]
Data Units Written:                 1,653,169 [846 GB]
Host Read Commands:                 17,918,106
Host Write Commands:                48,378,253
Controller Busy Time:               1,622
Power Cycles:                       55
Power On Hours:                     2,295
Unsafe Shutdowns:                   25
Media and Data Integrity Errors:    17,630
Error Information Log Entries:      17,630
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               36 Celsius
Temperature Sensor 2:               40 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0      17630    12  0x4395  0xc502  0x000       193760     1     -
  1      17629     3  0x2129  0xc502  0x000       193760     1     -
  2      17628     4  0x50d9  0xc502  0x000       272016     1     -
  3      17627    10  0x8388  0xc502  0x000       354832     1     -
  4      17626     3  0x410f  0xc502  0x000       272016     1     -
  5      17625     8  0x13ad  0xc502  0x000       272016     1     -
  6      17624    11  0x6021  0xc502  0x000       354832     1     -
  7      17623     5  0x2033  0xc502  0x000       272016     1     -
  8      17622     7  0x400c  0xc502  0x000       272016     1     -
  9      17621     3  0x111e  0xc502  0x000       354832     1     -
 10      17620     9  0x3094  0xc502  0x000       272016     1     -
 11      17619    11  0x3006  0xc502  0x000       272016     1     -
 12      17618     3  0x1125  0xc502  0x000       354832     1     -
 13      17617     7  0x102b  0xc502  0x000       272016     1     -

 

and when running `xfs_repair`
 

root@unraid:~# xfs_repair -v -n /dev/nvme0n1
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
.found candidate secondary superblock...
unable to verify superblock, continuing...
.found candidate secondary superblock...
unable to verify superblock, continuing...
.found candidate secondary superblock...
unable to verify superblock, continuing...
................................................................................Sorry, could not find valid secondary superblock
Exiting now.

 

I'm not entirely sure what this means but I'm guessing something has happened to the file system at some point? Potentially a bad disk? 

Edited September 18, 2022 by neutraltone
Additional discovery

[randommonth]

On 5/10/2022 at 7:40 PM, elcapitano said:

Cant get reverse proxy to work for organizr.

 

I am sorry having to ask for help on this, but I am at a loss.

 

Prereq: 

1) CNAME subdomain: "organizr.domain.xxx" has been created at cloudlare

2) Using SWAG - organizr.subdomain.conf has been configured (see attached)

3) SWAG restarted

4) Organizr is on docker's proxynet

5) Container name is "organizr"

 

What am I missing?

 

Container is up and running locally. .. 

 

 

Hi everyone, I was having the same problems with the same setup and found a solution that others may appreciate.

 

With the change of the Organizr app name to organizrv2, the "set $upstream_app" line should have organizrv2 in it.

 

I think the SWAG sample conf files need updating to reflect the change in app name.

 

 

[McTay]

 

Hi, 

 

My problem is that Tab Editor>Tabs don't load, everything else work.  Was working fine, until yesterday.  I hope someone can help me with this.

[CoZ]

I'm hoping the support for this isn't dead.  My Organizr keeps bugging me to update it for a while now.  I guess there was a new version released some time ago but the docker hasn't been updated to reflect it.

[Shu]

A separate problem here. For some reason, my organizrv2 container is backing up every week and this latest backup is taking up 152gb. Screenshot attached. Not sure why this is...

 

Edit: A few minutes later...I deleted all backups (except my first for...sentimental reasons) and manually created a backup - it was 627 kB. My guess and quick math is that the backups are backing up all previous backups as well. (Add up all those backups and it will roughly equal the size of the latest on, 152gb). 

Edited February 4, 2023 by Shu

[CoZ]

On 2/4/2023 at 12:12 AM, Shu said:

Edit: A few minutes later...I deleted all backups (except my first for...sentimental reasons) and manually created a backup - it was 627 kB. My guess and quick math is that the backups are backing up all previous backups as well. (Add up all those backups and it will roughly equal the size of the latest on, 152gb). 

 

What are you using to backup?  It looks like, from the screenshot, you are using some backup function from within Organizr?

 

I didn't know it had one until now.  I just use CA Appdata Backup / Restore v3 and backup all my dockers and their data.

 

Easier / simpler, FYI