[Support] Linuxserver.io - Nextcloud

[Tolete]

43 minutes ago, blaine07 said:

Is that with “latest” version of Collabora? Thank you!

 

58 minutes ago, Tolete said:

Collabora (latest)- 

[dius]

2 hours ago, Tolete said:

in NginxProxyManager-

specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.

On the SSL tab select a new certificate, enable HTTP/2.

I'm not the sharpest knife in the drawer, so forgive my ignorance, but how do you get to this NginxProxyManager?  I'm running swag on my unraid server, which incorporates Nginx, but I have never seen the interface you show in your post.

[ijuarez]

1 minute ago, dius said:

I'm not the sharpest knife in the drawer, so forgive my ignorance, but how do you get to this NginxProxyManager?  I'm running swag on my unraid server, which incorporates Nginx, but I have never seen the interface you show in your post.

NPM is a different reverse proxy manger

 

so is traefik.

[blaine07]

3 hours ago, Tolete said:

took a second look at this got it up and running.

 
steps i took--
 
reinstall/enable 'Nextcloud Office' (5.0.3) app.
 

 
Collabora (latest)- 
edit container and remove the 'Domain' Variable.
add  new Variable

save.
 
in NginxProxyManager-
specify https protocol and the server host/ip and port 9980. Also enable Websockets Support.
On the SSL tab select a new certificate, enable HTTP/2.

 
On the Advanced tab, enter:

# static fileslocation ^~ /loleaflet { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# WOPI discovery URLlocation ^~ /hosting/discovery { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# main websocketlocation ~ ^/lool/(.*)/ws$ { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host; proxy_read_timeout 36000s;}# download, presentation and image uploadlocation ~ ^/lool { proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host;}# Admin Console websocketlocation ^~ /lool/adminws { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass $forward_scheme://$server:$port; proxy_set_header Host $http_host; proxy_read_timeout 36000s;}

 

 
save and test.

Your pic shows “alliasgroup1”

Should it be as shown or “aliasgroup1” with ONE “l”?

 

edit: weird it only does work with TWO “l”. I don’t understand; I don’t see it expressed as anywhere with “alliasgroup” so don’t understand why that works. 🤦🏼‍♂️

Edited April 13, 2022 by blaine07
I dumb

[Tolete]

46 minutes ago, blaine07 said:

Your pic shows “alliasgroup1”

Should it be as shown or “aliasgroup1” with ONE “l”?

 

edit: weird it only does work with TWO “l”. I don’t understand; I don’t see it expressed as anywhere with “alliasgroup” so don’t understand why that works. 🤦🏼‍♂️

 

i have updated pic/post

 

documentation says/pic show 'aliasgroup1' the '|' in pic is just the cursor.

[blaine07]

Also, does anyone know where admin resides now? Can't seem to find it?

 

It used to be at "https://[IP]:[PORT:9980]/loleaflet/dist/admin/admin.html"

 

Now that 404s?

[blaine07]

Just now, Tolete said:

 

i have updated pic/post

 

documentation says/pic show 'aliasgroup1' the '|' in pic is just the cursor.

It didn't work for me with just one "l" but does with two? I dont understand lol

 

[Tolete]

17 minutes ago, blaine07 said:

It didn't work for me with just one "l" but does with two? I dont understand lol

 

 

what do you have for your collabora repository?

[dius]

I'm still trying to get Collabora & Nextcloud to work together.  Nextcloud shows that the Collabora server is reachable:

Yet I can't edit any documents using the Collabora server:

The swag log shows an error when I try to edit a document:

And I get this error showing up in the Collabora log file:

followed by several of these:

 

I know it's asking a lot, but I have no real clue how to troubleshoot this.  Any suggestions would be greatly appreciated.

 

Thanks in advance...

[blaine07]

25 minutes ago, Tolete said:

 

what do you have for your collabora repository?

I figured it out; had to enter alias like "https:/sub.domain.net:443"

 

Any idea on where ADMIN page lies now?

 

My repository: collabora/code:21.11.3.6.1

Edited April 13, 2022 by blaine07

[Tolete]

21 minutes ago, dius said:

I'm still trying to get Collabora & Nextcloud to work together.  Nextcloud shows that the Collabora server is reachable:

Yet I can't edit any documents using the Collabora server:

The swag log shows an error when I try to edit a document:

And I get this error showing up in the Collabora log file:

followed by several of these:

 

I know it's asking a lot, but I have no real clue how to troubleshoot this.  Any suggestions would be greatly appreciated.

 

Thanks in advance...

 

please see updated variable entry on my post.

 

[blaine07]

Oh, admin portal can now be found at: https://[IP]:[PORT:9980]/browser/dist/admin/admin.html

 

FOR REFENCE THE OLD ADMIN was: https://[IP]:[PORT:9980]/loleaflet/dist/admin/admin.html

[Tolete]

12 minutes ago, blaine07 said:

I figured it out; had to enter alias like "https:/sub.domain.net:443"

 

Any idea on where ADMIN page lies now?

 

My repository: collabora/code:21.11.3.6.1

 

see updated post.

[blaine07]

3 minutes ago, Tolete said:

 

see updated post.

See my post above about admin panel.

 

Does this: 

# Admin Console websocket
location ^~ /lool/adminws {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

 

need to change because admin URL changed?

 

EDIT: also, using above, is there a way to make the ADMIN page only accessible internally and not at all outside LAN?

 

 

Edited April 13, 2022 by blaine07

[Tolete]

5 minutes ago, blaine07 said:

See my post above about admin panel.

 

Does this: 

# Admin Console websocket
location ^~ /lool/adminws {
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_http_version 1.1;
  proxy_pass $forward_scheme://$server:$port;
  proxy_set_header Host $http_host;
  proxy_read_timeout 36000s;
}

 

need to change because admin URL changed?

 

EDIT: also, using above, is there a way to make the ADMIN page only accessible internally and not at all outside LAN?

 

 

 

post updated. new config

[dius]

38 minutes ago, Tolete said:

please see updated variable entry on my post.

Thanks for your response.

 

This is how I setup my aliasgroup1 variable.  I've tried it with the port 443 and without.  Neither works.

 

 

I'm using Swag as my reverse proxy, so the config files are different.  Would it help if I posted it here?

 

Thanks again for your response.

[JonathanM]

I just had a breakthrough, don't know if it's luck or the actual solution, but for me,

 

Key: alias_group1

Value: https://my\\.nextcloud\\.domain:443

 

worked, finally.

 

Apparently the _ between alias and group1 is quite important. Don't know how others have gotten it to work, but that's what did it for me.

[dius]

On 4/13/2022 at 1:34 PM, JonathanM said:

I just had a breakthrough, don't know if it's luck or the actual solution, but for me,

 

Key: alias_group1

Value: https://my\\.nextcloud\\.domain:443

 

worked, finally.

 

Apparently the _ between alias and group1 is quite important. Don't know how others have gotten it to work, but that's what did it for me.

Glad that worked for you.  Unfortunately it didn't work for me.

 

I'll keep plugging away...  

 

*UPDATE*

I got it working with a configuration I had previously tried but didn't work at the time.

 

I set the value for the alliasgroup1 key to https://mycloud.mydomain.org:443. This format now works for me.  Hopefully it helps others as well.

 

 

Edited April 18, 2022 by dius

[blaine07]

I just had a breakthrough, don't know if it's luck or the actual solution, but for me,
 
Key: alias_group1
Value: https://my\\.nextcloud\\.domain:443
 
worked, finally.
 
Apparently the _ between alias and group1 is quite important. Don't know how others have gotten it to work, but that's what did it for me.

What version Collabora you using?

[JonathanM]

6 minutes ago, blaine07 said:

What version Collabora you using?

 

[blaine07]

 

Yeah I don’t see the _ anywhere defined. I’m super confused by all this lol

[JonathanM]

2 minutes ago, blaine07 said:

Yeah I don’t see the _ anywhere defined. I’m super confused by all this lol

Neither did I, except in the logs as an error message. I was watching the collabora container logs in realtime as I attempted to edit a document, and it called out my FQDN and said it wasn't authorized in the alias_groups.

 

So I added 1+1 and got 3.

 

If that is indeed the case, and all the stuff I found online with aliasgroup1 is erroneous, I'm going to be rather upset that the internet wasted half my day. 🤣

 

All I know is, I made the change, and now it works, and no nastygrams in the logs about my domain not being authorized.

[blaine07]

3 hours ago, Tolete said:

 

post updated. new config

Is this new config supposed to make /admin not available outside LAN? I can't find any difference between what you initially posted for "Admin" and the new admin config?

 

Also, on bottom of Edit Proxy Host on NPM it says: 

 

 Please note, that any add_header or set_header directives added here will not be used by nginx. You will have to add a custom location '/' and add the header in the custom config there.

 

The config you have shared includes proxy set header directives? It says they wont work?

Edited April 13, 2022 by blaine07

[Tolete]

12 hours ago, blaine07 said:

Is this new config supposed to make /admin not available outside LAN? I can't find any difference between what you initially posted for "Admin" and the new admin config?

 

everything is running fine for me.

-not using _ or \\.//

 as for limiting the admin portal to local/lan only. no joy yet, have not gotten around it yet. Something like might work.

 

location ^~ /lool/adminws {
        return 404;
    }

 

Edited April 14, 2022 by Tolete

[PoppaJohn]

After an update (automatic) I can't get into my Next Cloud

The screen I am presented with has a white box with "New password" in it, and the button below says  "Reset password"

Looks like the file syncing on my PC is working, but I can't seem to message my buddy using the talk app anymore either.

I was really starting to get into NextCloud.