dius

Members
  • Posts

    31
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dius's Achievements

Newbie

Newbie (1/14)

5

Reputation

1

Community Answers

  1. Wow! I was only having problems accessing Nextcloud, so it never occurred to me to look at Swag. I followed these instructions, and also update my customized Nextcloud conf files and now everything is working. Thank you @sonofdbn for pointing this out to me. I'll try to remember to update the appropriate config files going forward.
  2. I wish I knew more about how this worked. I am seriously thinking about just deleting Nextcloud from my UnRaid server and starting over, but I'm not sure if that will solve anything. I'd like to get some other opinions first before I take such a drastic step.
  3. @sonofdbn I don't think those lines are significant. I have seen them from the very first time I started using Nextcloud. There definite differences in the config files, but that is due to your local setting etc. I don't know enough about the config options to know if there are any significant changes. I tried using the new sample config files, but it didn't make any difference. It looks like there may be an incompatible certificate now, but I have no idea how to figure that out.
  4. Since there doesn't seem to be any way to fix what has broken on my Nextcloud installation, I was wondering if I could simply remove it, then add it again. Would that solve my problem? For the benefit of anyone reading this, my Nextcloud service was working fine. I always accessed it using a domain. Just a couple of days ago, I was notified that there was an update to my Nextcloud docker so I went ahead and updated it. Nextcloud starts just fine. There are no errors in the log, however I can no longer access it. It doesn't matter if I use the domain or the IP address. The result is the same. It appears that there may be some kind of certificate issue but I have no idea how to debug it it and fix it. My thinking is that I may just remove it entirely from my Unraid server, then download and install a new one. I may lose all of my configurations, and may have to figure out how to get Collabora working again, but that may get me back up and running. Any other recommendations? Any help would be greatly appreciated.
  5. Thanks @Archonw for your help. In answer to your question, I always use a domain. If I click on Advanced and try to go to the site I get this error and can't go any further.
  6. I updated my Nextcloud docker container today, and now I am not able to connect to it. This is the error I get: Where should I look in order to try to diagnose this problem? I don't see any errors in the log file. Any help would be greatly appreciated.
  7. Thanks for the help. I was able to get everything working. I did a bit more reading and discovered that I had somehow managed to mess up a couple of settings in the management access settings. I set the User SSL/TLS to strict and enabled remote access. I then had to log out of the My Servers a pp, and log back in. That was the tricky part. At first it wouldn't let me log out, so I went to the website and logged out there. Then I was able to log out from my server. I then logged back in and suddenly everything was working and there were no errors. A wonder sight to see for sure. Thanks for your help. I was able to get it working. And yes I believe your suggestion was the trigger for me getting it working. From the look of things, the URLs were correct, but it made me did a little deeper. Thank goodness for documentation :).
  8. So I've been tweaking things a bit on my server - I no longer have the unsecure access problem. To fix that all I had to do was set the Use SSL/TLS in Management Access to Strict. That fixed that issue. As for the initial problem, I'm now seeing a message that says: JSON.parse: unexpected character at line 1 column 1 of the JSON data. Where can I locate this JSON file that is being parsed so I can find out what is going on? Any ideas? Thanks.
  9. After I followed the instructions to update my legacy SSL certificate, I started getting this error and can no longer connect securely to my server. I'm running Unraid 6.11.5. I see some unusual things in my Access Management page now too. Several warnings like this: When I click on the Learn More link, it just takes me to the Update Your Legacy SSL Certificate Now web page. I'd like to know where I should look to fix the unexpected token issue. Any ideas:
  10. 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.
  11. 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.
  12. 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...
  13. 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.
  14. Yes - using the local IP address of my server - I'm currently on the same network. However - just about 15 minutes ago, it started to work - I can now reach it remotely. I have no idea why, or what was wrong. I still can't get my Collarbora server to start though. I get a strange error logged when I try start it: --------------------------- Log snippet below ---------------------------- Generating RSA private key, 2048 bit long modulus (2 primes) .............................................................................................+++++ ...................+++++ e is 65537 (0x010001) Signature ok subject=C = DE, ST = BW, L = Stuttgart, O = Dummy Authority, CN = localhost Getting CA Private Key -e ERR: Use of domain variable is not supported. First host/domain who tries to connect to COOL is always allowed. To allow multiple host and its aliases use something like this and pass it as env variable: aliasgroup1=https://domain1:443,https://its-alias|its-second-alias:443 aliasgroup2=https://domain2:443,https://its-alias:443 For more info: https://sdk.collaboraonline.com/docs/installation/CODE_Docker_image.html ----------------------- End log snippet ----------------------------------- This is all I get each time I try to start it. I realize this is not the correct forum to try solve this problem, so feel free to point me where I need to go. Thanks.
  15. I upgraded Nextcloud the other day. I soon discovered that I could no longer reach my Nextcloud service. I was wondering how I could go about troubleshooting the cause of this issue, because it was working just fine before the upgrade. I applied another upgrade this morning hoping it would solve the problem, but it still persists. The log doesn't show any problems, so I'm not sure it has anything to do with the upgrade. Thanks for any pointers or suggestions. I have just noticed that my Collabora server is not working. I don't know if that could be why I'm not able to reach Nextcloud (I rather doubt it, but thought I'd mention it just in case). Another update: I can reach Nextcloud by directly typing in the IP address of my Unraid server, but not using duckdns, like I used to be able to do. I'm guessing that it's a problem with the reverse proxy somehow.