Organizr v2 just broke with an automatic update to v2.1. | PlexGuide.com

Organizr v2 just broke with an automatic update to v2.1.

  • Stop using Chrome! Download the Brave Browser via >>> [Brave.com]
    It's a forked version of Chrome with native ad-blockers and Google's spyware stripped out! Download for Mac, Windows, Android, and Linux!
Welcome to the PlexGuide.com
Serving the Community since 2016!
Register Now

fyrstrm

Experienced
Original poster
Donor
May 1, 2020
98
32
It appears that I need some sort of fix for Organizr. With the deployment of the new v2.1 api, it has broken the database evidently. Anything in the works or any advice?
 
  • Like
Reactions: 1 users

Malykai

Citizen
Aug 12, 2018
3
5
@fyrstrm You beat me to posting it, discovered it broken last night and been working on trying to get it working today so far without luck. It looks like they moved from using organizrtools to organizr. I have stood up that docker but when I try to use the new image with the original config folder it breaks and I haven't had enough time to dig through it myself yet to find the issue.
Post automatically merged:

@fyrstrm I finally got mine to load with the original organizrtools repo by just changing the default file in /opt/appdata/organizr/nginx/site-confs/ I added the 3 lines below the location.
Code:
server {
        listen 80 default_server;
        root /config/www/Dashboard;
        include /config/nginx/healthcheck.conf;
        index index.html index.htm index.php;

        server_name _;
        client_max_body_size 0;

        location / {
                try_files $uri $uri/ /index.html /index.php?$args =404;
        }
        location ~ \.php$ {
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                try_files $fastcgi_script_name =404;
                # With php5-cgi alone:
                fastcgi_pass 127.0.0.1:9000;
                # With php5-fpm:
                #fastcgi_pass unix:/var/run/php5-fpm.sock;
                fastcgi_index index.php;
                include /etc/nginx/fastcgi_params;
                fastcgi_hide_header X-Powered-By;

        }
        location /api/v2 {    # Added from here to the first } below
            try_files $uri /api/v2/index.php$is_args$args;
        }
}
Post automatically merged:

Now I have to figure out the API calls to permit access to the other dockers. I have been using the organizr api to authenticate based on the groups assigned to users in there.
 
Last edited:
  • Like
Reactions: 2 users

fyrstrm

Experienced
Original poster
Donor
May 1, 2020
98
32
Thanks so much for this; that fixed mine. Let me know how the API part goes but really appreciate the fix!
 

Malykai

Citizen
Aug 12, 2018
3
5
No problem... Glad I was able to get it working. I did manage to get my API working earlier as well... I had to adjust the labels on my dockers for authentication: "traefik.frontend.auth.forward.address"
The old way of doing the API was like this:
Code:
     http://organizr:80/api/?v1/auth&group={GROUP_NUMBER}
With the new version it will be:
Code:
http://organizr:80/api/v2/auth?group={GROUP_NUMBER}
I just manually updated most of them for now, but I'll have to update my playbooks in case I need to rebuild it in the future.
 

crustyakorn

Experienced
Aug 30, 2018
59
23
Thanks for the tips here.

Still struggling to get it working even tried deploying via PG commands in Terminal and it still fails. Updated the config file as mentioned above but it doesn't work.
I think the main community config would need some rework ..
 

tattoomees

Active
Donor
May 4, 2018
36
10
opened container pressed duplcate/edit changed image there organizr/organizr:latest
then pressed deploy the container then it askedf replace i pressed replace

wait few minutes then refresh your page
 

corvux

Citizen
Donor
Dec 1, 2019
9
3
opened container pressed duplcate/edit changed image there organizr/organizr:latest
then pressed deploy the container then it askedf replace i pressed replace

wait few minutes then refresh your page
do the same no luck, says unhealthy.
 

tattoomees

Active
Donor
May 4, 2018
36
10
then u need try restore it from backup from pgvault
Post automatically merged:

If you modified the default Nginx file, and the startup script didn't manage to add the /api/v2 location, add the configuration as described below, or recreate the default by deleting it.
 
Last edited:

jim2fast4u

Citizen+
Jul 12, 2018
20
5
Thanks for the steps @Malykai

I tried several steps to get this working following this thread and ended up with the following procedure:

1. remove Organizr
2. Restore from Vault
3. Edit default file with info from @Malykai
4. install organisr

This seems to have made it functional at a base level.
 
  • Like
Reactions: 1 users

leedavidpointon

Citizen
Sep 15, 2020
3
1
It appears that I need some sort of fix for Organizr. With the deployment of the new v2.1 api, it has broken the database evidently. Anything in the works or any advice?
i deleted organizr container and appdata folder, then i opened 2 sessions of ssh the first one i went into community apps ready to install organizr the second one i edited the organizr yml file and changed the image to organizr/organizr, then i install organizr from the install community apps window, i did it this way because when you edit the organizr yml file and then open pg community apps it updates back to the old image. not sure if this way will stay working but so far so good
 
  • Like
Reactions: 1 user

evlo

Active
Feb 13, 2020
32
6
I get this error even thought I installed organizr for the first time using plexguide right now, so there should be nothing to migrate, right?

I tried
pgbox - remove organizr
verified nothing is in opt/appdata
reinstall organizr
to be sure it was fresh install


adding
Code:
location /api/v2 {
            try_files $uri /api/v2/index.php$is_args$args;
        }
to
Code:
server
section of
Code:
/opt/appdata/organizr/nginx/site-confs/default
did help
 
Last edited:
  • Like
Reactions: 1 user

Xeizez

Citizen
Feb 17, 2020
14
1
opened container pressed duplcate/edit changed image there organizr/organizr:latest
then pressed deploy the container then it askedf replace i pressed replace

wait few minutes then refresh your page

tried this and it worked for me
 

evlo

Active
Feb 13, 2020
32
6
Ok, now I understand that the docker repo changed, but changing image to organizr/organizr:latest my container fails to start up, even going back, so maybe I messed up something else, nothing useful in the log, I guess I will wait for the new plexguide release.

edit: well in the docker state there is this
Code:
curl: (22) The requested URL returned error: 404 Not Found curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
 

Recommend NewsGroups

      Up To a 58% Discount!

Trending