REllU

Hey all, I got myself in a quite a bit of a trouble.. I tried to update Nextcloud to the latest stable build through the UI, but it failed. I was able to get everything fixed with the help of this: and then manually moving the files from the Backup folder to their correct locations. But! There was another update. I thought, surely this time it would work. It didn't. I tried to do the update through the terminal again, but this time around, I'm stuck in a "Internal server issue" page. In the log, there is one particular error that keeps showing up: I've battled with this for hours now, and it's getting late. I'm hoping I can get this fixed through the weekend, since my team is going to need to use Nextcloud again next week. Any help would be greatly appreciated!

I went through this few weeks ago, I can't quite remember how I ended up with this one, but the "onlyoffice document server" from "Jidovu Marius Adrian's Repository" works for me.

@skois@whitedwarf Update on the situation. I ended up buying Ubiquiti's UniFi USG, setting our Huawei modem to work in Bridge mode, so that the USG is the main router, and after the basic setup, everything just worked. NAT Loopback finally works, I can access my server through the domain name within the same network, and with that, OpenOffice connected with NextCloud without any issues at all. I can finally breath!

I've read about this approach, and if it was just me at the office, that'd probably be fine. But we have a bunch of PC's in there, and the idea of "hard coding" such a thing into each machine doesn't sound too great. Also, I don't think that'd still help with the issue of trying to get OnlyOffice to sync with UnRaid

@skois @whitedwarf I watched through the Spaceinvadeone's video about setting up reverse proxy, and that indeed confirmed my hunch. Your modem is required to have NAT Relfection / Hairpinning / loopback, in order for the setup to work properly, and the domain name to be accessed from the same network. I'm a bit upset, as we _just_ bought a new modem to the office, but it's a consumer grade one, so it doesn't have these features. So I'll just have to figure out what kind of a modem we actually need, and how to get everything to work on out network the way we need. Oh well...

My understanding here, is that while the domain does indeed has it's own IP (of the domain server), it does still redirect your browser to our public IP, where our UnRaid server is. From there, it's supposed to be picked up by the proxy, and then re-directed to the correct local-ip. However, it never reaches the proxy, since again, my modem doesn't support hairpinning, meaning that when it gets asked to redirect a website to the same IP address the modem itself has, it doesn't know what to do with it. (I'm sure there's a better explanation of this, but I don't have the understanding to really dig that deep into this) So what ends up happening, is that my domain does redirect the request to our public IP, our modem gets the request, and doesn't know what to do with it from that point on. Proxy never gets the request to redirect it. I didn't set up my NextCloud with Spaceinvaderone's video, as that didn't seem to work for me. Instead, I used this guide to set everything up: https://medium.com/@chrismorris_82249/setup-a-reverse-proxy-nextcloud-server-on-unraid-using-letsencrypt-831905d94f7d Within that guide, it shows how to create your custom network within UnRaid, like so: docker network create <networkname> I did this, and the dockers are indeed within this same network. I do remember seeing some more configurations being done to such a network in somewhere, on top of just creating one.

Sorry for the late response. I wasn't able to find a line for "rejectUnauthorized" in the default.json file at all Unfortunately, I don't have time anymore to really do any more trobleshooting with this, so I'll probably have to give up and continue using Google Docs/Sheets until our current project is done and I have a bit of time in my hands again. I still feel like my issue has something to do with me not being able to connect to NextCloud within the same network. Not about the certificates, but how our network is setup. Again, the modem we have does not support hairpinning, and we don't have a way to create vlan:s at this point. Could someone confirm if someone else got OnlyOffice or Collabora to work without hairpinning or setting up a vlan to their network?

I'll look into this more, and try out using the certificates from cPanel! Just to clarify though, I do have certificates from letsencrypt, and they seem to be working outside of the network just fine, as I'm able to get a secure connect to both, OnlyOffice server as well as NextCloud outside of the network. I'll report back once I've tested cPanel certificates!

Sorry for the slow response! I'm able to create certificates for my domains and cnames through cPanel, but I didn't think these were used, as you can do certificates with letsencrypt? If this was the root cause, it would make some sense though. After creating the certificates on cPanel, would I need to download them somehow, and add them to NextCloud and OpenOffice? I'm not entirely sure how that's done. tracert documentserver.mydomain.com spits out: C:\WINDOWS\System32>tracert documentserver.mydomain.com Tracing route to nextcloud.mydomain.com [public IP] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mobile-user-c1d052-180.dhcp.inet.fi [public IP] Trace complete.

I'd be fine using Google Docs myself if it was for personal use. But I'm setting up our server for our company use, and my dream is to try to have everything in one place, a "hub" area, if you will. That's why I still keep banging my head against the wall, hah! @skois, I think I've gotten a bit further with this whole thing. I added 'allow_local_remote_servers' => true, into the config.php (of Nextcloud), and with that, I was able to get a bit different results while trying to connect with OnlyOffice. With documentserver.mydomain.com the error was same. But when I tried to connect directly with the local IP and port, the error changed to: Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 5.4.2.46) Googling this a little bit, I stumbled upon wget command, for checking if the two dockers would be able to communicate with each other at all. First of all, I tried wget google.com, which worked on both applications. After that, I tried to wget <other docker domain>, and got failed: Connection refused. After which, I tried wget <local ip address of the other docker>, and with that, I got: ERROR: cannot verify <NextCloud IP>'s certificate, issued by ‘CN=*,OU=LSIO Server,O=Linuxserver.io,L=Carlsbad,ST=CA,C=US’: Self-signed certificate encountered. ERROR: certificate common name ‘*’ doesn't match requested host name ‘<NextCloud IP>’. To connect to <NextCloud IP> insecurely, use `--no-check-certificate'. I was hoping to manage the whole self-signed certification thing later, but maybe that'd be my next step then.. Also, all of this to me is just enforcing my hunch that not being able to access nextcloud.mydomain.com within the same network doesn't work. If I were to solve that, I have a feeling I might be able to get forward. If I may ask, what provider do you use for your domain? Would it be possible that my domain host just doesn't support some feature that was required to make this work?

Thank you so much for these! I'm exhausted for today, but I quickly tried to change the nginxproxymanager settings similar to yours, went back and forth between OnlyOffice and Collabora, tried with certificates and disabling them, with cnames and with direct IP's, and nothing changed unfortunately. I also tried with Bridge network mode, and with the custom network. At this point, I'd be happy with either Collabora or OnlyOffice honestly, hah! Is there any chance something weird might've happened when I got the new modem in to the office? It's basically the same one as we had previously, but just the better and newer model of it. After the new modem, the error changed from "cURL error 7: Failed to connect to xxx.xxx.xx port 8443: Connection refused " to the one it's now, "Error when trying to connect (Bad healthcheck status)" Again, I do appreciate all the help! If there's anything else you can think of, let me know! I'll try to go through all of the settings you have here in more detail tomorrow, and see if there's anything I missed.

Was _just_ editing my previous message, hah! I went ahead, and gave Collabora a shot. I tried to connect NextCloud with Collabora through collabora.mydomain.com, but the connection didn't go through. Then I tried to put the local IP address, with Collabora's port in there, and that semeed to do the trick! Connection seems to be established now. Though, that victory was short lived. Trying to open a document file (or creating a new one) results in either time-out (with the application IP), or to a "Failed to read document from storage" I don't have too much time to troubleshoot this further, but with a quick google search some people had problems with outdated PHP version. This doesn't seem to be the case with me, as my PHP version is 7.3.25, which is a newer one than those having the issues. I'll try to change all networks to Bridge, and see how that goes. Will report back soon. EDIT Changing all Docker network types to Bridge seemed to make no difference.

Sorry for the late response, had to catch some sleep between the days! Almost got excited for the overwrite.cli.url, as I figured that'd maybe help with the access to Nextcloud within the same network, but no Anyway, I changed the overwrite.cli.url, which didn't help. After which I checked the settings within nginxproxymanager (screenshots of the settings here), and I'm guessing having the protocol set as https should force it to use https? I also tried to force SSL on the other page, to no help unfortunately. If OnlyOffice is no go, I'd be happy with Collabora. But I feel that there's something else going on with my server, since I couldn't get Collabora working either. It just wouldn't connect from NextCloud. Though, I didn't give it as much thought as for OnlyOffice, as getting excel files would be a really big deal for us. By any chance would the issue be some settings within my modem? (NAT, hairpinning, VLAN? Throwing in buzzwords I've heard about before) If it's a hardware issue, I'd be OK buying a new switch or something if it meant that this issue would be fixed. But so far, from all the googling and searching I've done, I don't think this has anything to do with the issue I'm having..? Still, I appreciate your help! Thank you!

Hey, onlyoffice.mydomain.com (I've named it as documentserver.mydomain.com) does work, and can be pinged from the NextCloud console. I'll attach the files in this message, hopefully it's all that's needed here. I changed the domain names, and IP addresses etc to "XXXX" The repository for OnlyOffice is set up as onlyoffice/documentserver:6.0 as I've gone through a looooot of messages today, and I've been trying out a-lot of different fixes, one of which was to download the old 6.0 version instead of the newest one. As you might've guessed, that didn't work either Ps, it already feels so much nicer knowing there's another pair of eyes going through my misery. Thanks! NextCloud configuration file (NginxProxyManager).conf OnlyOffice configuration file (NginxProxyManager) .conf nextcloud_config.php

Hey there! Yes, the healthcheck is indeed showing within NextCloud. From NC's own logs, the opened up error is: Exception: Bad healthcheck status /config/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 168: OCA\Onlyoffice\DocumentService->checkDocServiceUrl(OC\URLGenerator {}, OCA\Onlyoffice\Crypt {}) /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 169: OCA\Onlyoffice\Controller\SettingsController->SaveAddress("https://doc ... /", "", "", true, "", false) /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 100: OC\AppFramework\Http\Dispatcher->executeController(OCA\Onlyoffi ... {}, "saveAddress") /config/www/nextcloud/lib/private/AppFramework/App.php - line 152: OC\AppFramework\Http\Dispatcher->dispatch(OCA\Onlyoffi ... {}, "saveAddress") /config/www/nextcloud/lib/private/Route/Router.php - line 309: OC\AppFramework\App::main("SettingsController", "saveAddress", OC\AppFramew ... {}, { _route: "o ... "}) /config/www/nextcloud/lib/base.php - line 1008: OC\Route\Router->match("/apps/onlyo ... s") /config/www/nextcloud/index.php - line 37: OC::handleRequest() Should've put that into the original post, sorry >.>

I think I got myself even more stuck now. We replaced our modem today for a newer one, got everything set up for it, and everything seems to be working as usual. NextCloud can be accessed outside of the network, and so can OnlyOffice. However, now I'm greeted with "Error when trying to connect (Bad healthcheck status)" within NextCloud when trying to save the settings of OnlyOffice. Again, the demo server of OO works just fine. I've tried to replace SWAG with NGinxProxyManager, I've copied the cert files (and tried without copying them), I've replaced the OnlyOffice docker from chvb's to the one from Siwat2545, but the only thing that changed from all this, is that now I'm no longer getting the green check mark when accessing onlyoffice.mydomain, but instead I'm getting the "welcome" screen of OnlyOffice. (Without copying the cert files, I get 502 Bad Gateway) I know I'm in deep waters here (for me), so I'd be more than happy to compensate any help with some donations (if that's allowed here) I'd really appreciate any help, or even just someone telling me that it doesn't work right now so I could stop banging my head against the wall.

Hello everyone, I hope I'm doing this in the right place. My issue is, that when I'm trying to set up OnlyOffice within Nextcloud, I'm getting: " Error when trying to connect (cURL error 7: Failed to connect to xxx.xxx.xx port 8443: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html))" I've set up a cname for onlyoffice through cpanel, and connecting to onlyoffice directly from the web gives me a "Document server is running" message. However, if I try to connect within the same network as the UnRaid server is in, I get an error. My guess is, that this is the reason why I can't connect to OnlyOffice through NextCloud? (NextCloud in itself doesn't work on the same network either, as my modem doesn't support hairpin / vlan unfortunately) Trying to setup the demo Document Server everything works just fine. But obviously, this is not what I'm after. I'm using SWAG (nginx) to reverse-proxy both NextCloud as well as the OnlyOffice docker, and like I've stated, both work nicely from outside of the network. I've created a custom network within Unraid for all of these apps, so that they'd be able to talk with each other. As for how I tried to setup the OnlyOffice, I followed Spaceinvader one's tutorial video. Before that, I tried to install Collabora with no luck (not getting any specific errors, but I'm suspecting the issue was the same) before giving up on that, and moving to OnlyOffice. I haven't tested the Community Document Server directly from Nextcloud, but based on the reviews and things I've read online, I'm not too convinced I should even try that. As for UnRaid, I only have OnlyOffice (named as "documentserver"), mariadb, nextcloud, and swag installed as dockers. (This server will be used as file server, Google Drive replacement, if you will, for our company) I'm really new to servers, and networking in general (which you'll probably be able to tell), so there's a chance I've setup something very obvious incorrectly, but my knowledge of all this just seems to be not enough. I'd really appreciate any help for this.