On 8/13/2020 at 10:29 PM, Jessie said:

To me, this looks ok. I've never used dns validation though.  Is there any reason you can't use http?  What do the letsencrypt logs look like.  Were the certificates generated?  If they were and it still doesn't work then blow the letsencrypt docker away. Remove files and reinstall a fresh one.  Don't know why but it works for me sometimes.

Dont forget to forward ports 443 and 80 in the router. (443ext to 1443 int) and (80ext to 180 int)

Hi, so for the reason I can't use http is there is an error in my Letsenrypt log (same error as shown in the 1st version of SpaceInvander Reverse Proxy video). I think my ISP blocked port 80. Thats why I proceed with dns verification.

 

ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

 

However, there was no error in my log after using dns verification. And stated server ready at the end. Yes I port forward port 80 to 180, 443 to 1443 with TCP/UDP. Just a note, if I only port forward with TCP only of 80 to 180 to my unraid server. I was kick out of my unraid server interface for some reason. But TCP/UDP works for me regardless if is need TCP only. Yes, it is still stuck in the Letencrypt WebUI after setting up Letsencrypt docker again. So I can conclude that my ISP blocked port 80. It is still possible to work with Letencrypt without port 80? 

 

Let say I dont want to use Reverse Proxy anymore to redirect me to my docker container, do I have another option to try with step by step guide? Cause my purpose is really to get onlyoffice working with nextcloud, can I get onlyoffice to work without reverse proxy?

Edited August 16, 20205 yr by Wong

Hi, i moved my "data path" from cache disk to the normal "data" pool. This works fine, but the i'm not able anymore to spin down all disk, because it looks like nextcloud permanently writes to the data path.

Does anyone has a solution for that?

thx

14 minutes ago, Wong said:

Hi, so for the reason I can't use http is there is an error in my Letsenrypt log (same error as shown in the 1st version of SpaceInvander Reverse Proxy video). I think my ISP blocked port 80. Thats why I proceed with dns verification.

 

ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

 

However, there was no error in my log after using dns verification. And stated server ready at the end. Yes I port forward port 80 to 180, 443 to 1443 with TCP/UDP. Just a note, if I only port forward with TCP only of 80 to 180 to my unraid server. I was kick out of my unraid server interface for some reason. But TCP/UDP works for me regardless if is need TCP only. Yes, it is still stuck in the Letencrypt WebUI after setting up Letsencrypt docker again. So I can conclude that my ISP blocked port 80. It is still possible to work with Letencrypt without port 80? 

 

Let say I dont want to use Reverse Proxy anymore to redirect me to my docker container, do I have another option to try with step by step guide? Cause my purpose is really to get onlyoffice working with nextcloud, can I get onlyoffice to work without reverse proxy?

You don't need port 80 at all. And this should be in the letsencrypt thread and not here.

https uses port 443 for all communication.

4 minutes ago, saarg said:

You don't need port 80 at all. And this should be in the letsencrypt thread and not here.

https uses port 443 for all communication.

Ohh my bad. I am sorry.

1 hour ago, malac said:

Hi, i moved my "data path" from cache disk to the normal "data" pool. This works fine, but the i'm not able anymore to spin down all disk, because it looks like nextcloud permanently writes to the data path.

Does anyone has a solution for that?

thx

I think if the .log and the .db files should stay in the "config" path, then everything should be fine....

1 hour ago, malac said:

I think if the .log and the .db files should stay in the "config" path, then everything should be fine....

That is not something we can control.

On 8/16/2020 at 2:48 PM, saarg said:

That is not something we can control.

but normally log file are located in appdata,or?

On 8/17/2020 at 3:43 PM, malac said:

but normally log file are located in appdata,or?

Normally, but I don't know about next nextcloud.

The database depends on the setup. If you use an external database, it will be in that softwares appdata and if you use sqlite, please don't as it's  slooow, it's in the data volume.

On 8/16/2020 at 8:11 PM, saarg said:

You don't need port 80 at all. And this should be in the letsencrypt thread and not here.

https uses port 443 for all communication.

If you use the http method, letsencrypt requires port 80 for validation when it generates the certificates.

443 is used for communication, but no port 80 = no certificate.

 

On 8/16/2020 at 7:55 PM, Wong said:

Hi, so for the reason I can't use http is there is an error in my Letsenrypt log (same error as shown in the 1st version of SpaceInvander Reverse Proxy video). I think my ISP blocked port 80. Thats why I proceed with dns verification.

 

ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

 

However, there was no error in my log after using dns verification. And stated server ready at the end. Yes I port forward port 80 to 180, 443 to 1443 with TCP/UDP. Just a note, if I only port forward with TCP only of 80 to 180 to my unraid server. I was kick out of my unraid server interface for some reason. But TCP/UDP works for me regardless if is need TCP only. Yes, it is still stuck in the Letencrypt WebUI after setting up Letsencrypt docker again. So I can conclude that my ISP blocked port 80. It is still possible to work with Letencrypt without port 80? 

 

Let say I dont want to use Reverse Proxy anymore to redirect me to my docker container, do I have another option to try with step by step guide? Cause my purpose is really to get onlyoffice working with nextcloud, can I get onlyoffice to work without reverse proxy?

In unraid, I set Use SSL/TLS: to no.  (In settings/Management access) This means I access unraid via the ip address and it stays fully enclosed within my network.  To get to it from outside, I use ipsec tunnels.  This frees up port 443 for letsencrypt.

 

So I pass port 443 through letsencrypt intact.

It might be interesting to see if that works.  It would prove beyond doubt if port 80 is blocked.  I still redirect port 80 to another port. eg 180

 

If port 80 is blocked, it is possible you might be able to unblock it by logging into you ISP user area.  In Australia IInet block it but you can optionally turn blocking off.

 

If using dns verification port 80 is irrelevant.  If the log said server ready, it sounds like it generated the certificate.

 

It is important not to miss that step in spaceinvaders tutorial about "proxynet". After you create it, you need to point Mariadb, nextcloud, letsencrypt and onlyoffice to it in your docker settings rather than "Bridge".

 

The letsencrypt proxy will allow you to run multiple servers through the same isp IP address.  eg Multiple Nextcloud instances, collabora, onlyoffice and any other docker or vm which require port 443.  Otherwise you would require multiple ISP addresses.

On 6/30/2020 at 2:57 AM, gacpac said:

Hi I've had a problem since forever and nobody seem to care. 

 

Does someone knows how to get rid of this problem message preventing me to upload files bigger than 50MB?

 

Server replied "413 Request Entity Too Large" to "PUT https://nextcloud.mydomain.com/remote.php/dav/uploads/myprofile/213883260/00000001" 

 

 

Had a problem like that a long time ago.

 

Use notepad++ and have a look in appdata/letsencrypt/nginx/proxy.conf

 

At the top there should be a line 

# client_max_body_size 2048m;

If it doesn't read 2048m, make it 2048m.

 

or as above block that line out with a #

I've found max filesize will be 2gb when you drag it to the web interface, but unlimited if the client does the transfer.

 

Had a problem like that a long time ago.
 
Use notepad++ and have a look in appdata/letsencrypt/nginx/proxy.conf
 
At the top there should be a line 
# client_max_body_size 2048m;
If it doesn't read 2048m, make it 2048m.
 
or as above block that line out with a #
I've found max filesize will be 2gb when you drag it to the web interface, but unlimited if the client does the transfer.
 

Thanks I was able to fix it by looking at the github website and found that developers removed the max_body_size in future releases.

Removed the little line in my setup and all perfect now

https://github.com/nextcloud/d...ues/762#issuecomment-504225433

Sent from my Pixel 2 XL using Tapatalk

8 hours ago, Jessie said:

If you use the http method, letsencrypt requires port 80 for validation when it generates the certificates.

443 is used for communication, but no port 80 = no certificate.

 

He said he was using DNS verification, so he don't need port 80. And this belongs in the correct thread, not here.

4 hours ago, saarg said:

He said he was using DNS verification, so he don't need port 80. And this belongs in the correct thread, not here.

Point taken, but at the end of the day it is really about getting nextcloud working. The fault could be in either.

My gut feeling is the problem will lie in the port 443 to 1443 translation. 

 

Hi, just installed LSIO Nextcloud on Unraid 6.9.25.  Just nextraid and mariaDB at the moment.  No letsencrypt/reverse proxy yet.  Did a photo sync from the mobile app and it worked great.  But tried to comment on a photo from mobile gives me a strange 405 error.  Any ideas?

 

I installed this from Community Applications, and it just worked. 

I also have a reverse proxy set up.

Can I just use it "out of the box" or do I need to go through the setup described in the OP (e.g., MariaDB)? 

Do I need to change anything in the configuration file?

I've been running it like this for a few days, and it seems to work great. 

Should I delete this docker and start over with the more extensive set up instructions?

Thanks.

1 hour ago, volcs0 said:

I installed this from Community Applications, and it just worked. 

I also have a reverse proxy set up.

Can I just use it "out of the box" or do I need to go through the setup described in the OP (e.g., MariaDB)? 

Do I need to change anything in the configuration file?

I've been running it like this for a few days, and it seems to work great. 

Should I delete this docker and start over with the more extensive set up instructions?

Thanks.

If you didn't go through the setup, you have already set it up at an earlier point.

Could someone please help me with a strange issue I am having.

It relates to external storages using SFTP.

There are two issues. First (and this isn't that important for now) is that using RSA private key doesn't work. No matter how I configure it, it says cannot read key (RSA 4096 key, generated in linux via ssh-keygen, that connects in fine).

Secondly, and this is a lot more concerning, and I am completely stuck:
Using RSA public key, created by NC, I can connect to external shares, and upload files. But I cannot then download those files again (accessing the server directly, the files are fine, I can download them through other means, they work etc)

Logs are pointing to SFTP.php as the culprit, but that's literally as far as I am able to get. For example:

 

Here is trying to save a file I uploaded

```

 Error: fopen(sftpread://home/[username]/public//gba.7z): failed to open stream: "OCA\Files_External\Lib\Storage\SFTPReadStream::stream_open" call failed at /config/www/nextcloud/apps/files_external/lib/Lib/Storage/SFTP.php#378

GET /remote.php/webdav/[username]Share/gba.7z?downloadStartSecret=[11 character code]
from [IP] by [username] at 2020-08-26T08:13:59+00:00
```

line 378 is
$handle = fopen('sftpread://' . trim($absPath, '/'), 'r', false,

There are other errors for opening files, trying to save uploaded files, copying uploaded files.
Basically anything to do with interacting with a file that's been uploaded to the external share (all SFTP shares) via NC

 

Edited August 26, 20205 yr by 4554551n

6 hours ago, saarg said:

If you didn't go through the setup, you have already set it up at an earlier point.

I never did any manual setup.

What I did do is install the NextCloud official from Community Applications.

It did not have a GUI - so I deleted that docker and installed the Linuxserver Nextcloud.

As soon as I installed it, it just worked. No configuration needed.

So, is it possible that my first install set up the database? I don't really understand what happened, but I not have a working instance of NextCloud using the default Linuxserver settings.....

Thanks.

Anyone had success with the built-in Collabora environment (CODE) in v19.x?

 

I'm having trouble connecting to the new built-in CODE server and I wonder if it has something to do with nginx config. I'm using nginx proxy manager so I'm not sure how to properly edit the config to allow access, e.g. according to this post: https://www.collaboraoffice.com/online/connecting-collabora-online-built-in-code-server-with-nginx/

My nextcoud docker isn't accessible anymore on the web interface. Had some problems with the pm.children. Didn't seem to fix it. So now I want to fix it through php.ini but my php folder is empty. Where can I find that config? Or the php files for that matter.

Hi, 

 

I was hoping that someone could give me a steer in the right direction. 

 

I have NextCloud setup and everything is great, when I access it via proxy, however when accessing locally, I get a Strict-Transport-Security error. Its not a massive problem, however I would like to learn why this is happening. 

 

For reference, I've added "add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload;" always;" to the "default.conf" in NextCloud but that hasn't made any difference. 

 

Regards. 

 

 

When accessing locally;

 

Accessing via proxy;

 

Default.conf file;

Edited August 30, 20205 yr by LoneTraveler

hi,

i'm using this docker for nextcloud and another container for onlyoffice. The container i use seems to be not maintained anymore (siwat's repository).

It's still working in a web session but i'd like to change to a more actual version.

Do you have any suugestion for onlyoffice docker repository?

If i could keep my onloffice appdata it would be convenient.

 

Hi there I have searched and found two times where someone has had a similar problem but I cannot find the solution. 

I keep receiving this error in the log file

2020/09/01 19:36:33 [error] 372#372: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.23, server: _, request: "GET / HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.0.11:444"

and when I tried to go into the GUI 

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

I assumed this was due to IP address being incorrect so I went into the config and amended it to to match the below. 

However I still get an error trying to connect. I am now stuck. I have enabled debugging but cant seem to see a file. Appreciate any help. I am not sure if its potentially an issue with mariadb or nextccloud itself. 

 

 

20 hours ago, caplam said:

hi,

i'm using this docker for nextcloud and another container for onlyoffice. The container i use seems to be not maintained anymore (siwat's repository).

It's still working in a web session but i'd like to change to a more actual version.

Do you have any suugestion for onlyoffice docker repository?

If i could keep my onloffice appdata it would be convenient.

 

wow, i don't know where i saw this but i'm using onlyoffice repository.

Yesterday i had hard time trying to maake this work. Onlyoffice was not available (even locally) until i fixed the reverse proxy problem i had (deleted linuxserver/let's encrypt and reconfigured from scratch linuxserver/swag).

Strange but it's now working