blaine07

Members
  • Posts

    382
  • Joined

  • Last visited

Everything posted by blaine07

  1. PSA: Not sure if anyone tried to the new Collabora Code(6.4.13.1) released 17 hours ago but it wouldn’t work for me on NC 22.1.1(I need to upgrade to 22.2.0). I downgraded Collabora to collabora/code:6.4.11.3 and immediately had success loading documents 😬🤨
  2. Is their a nginx/SWAG proxy conf template for exposing this to outside word?
  3. Anyone else seeing basically persistent "connection error" with this? I open it in browser and every 15-20 seconds it pops up. Not seeing anything prevalent in logs. Anyone have any ideas at all?
  4. SSL stuff doesn't seem to work/be applicable to my setup. Everytime I had any of the SSL stuff it gave a error about SSL going to http port or something silly. None the less, tried every combination of with and without things you provided and STILL ended up back on 6.4.9.3. I guess maybe this should've been asked long ago but what version of NC are you on--21.0.3 here? Do you think the NC helper "app" installed in NC could be part issue? Should "cert_domain" and "server_domain" be same? I think the answer is NO>?
  5. Skois, Would I need to add the don’t get SSL cert parm like in your pic too?
  6. Skois, still no dice. Ugh. No idea what’s wrong. Maybe I need to wipe container and start over. Ugh I dunno [emoji30]
  7. Will report back. Yes did do .9 I fat fingered what I typed. .9 should show in pic I think. None the less yes maybe the 1 slash thing is it. Thanks so much; will report back soon
  8. Uptime Kuma been working fine(once I figured out my last post)...then today random 403 error. Made NO configuration changes... ;facepalm; EDIT: disregard; im a idiot sigh... LOL
  9. So, still no dice upgrading to 6.4.10.3. I downgrade to 6.4.9.3 and it immediately works fine. Collabora must have changed something specific that inadvertently affects the functionality of mine in which the current way it is configured. Any idea where I can find change logs that would potentially elude me to what may have changed on their end? Taking a quick gander do you see anything totally Awry on my part? (Been SO long since I set it up; it's just always worked but I think initially some years ago I had used SI1's config tutorial) Edit: don’t see anything useful here https://www.collaboraoffice.com/code-6-4-release-notes/ Could issues be related to newest version of Collabora AND the newest plugin app thing you have to install in Nextcloud to use Collabora as a WOPI or whatever? NC V 21.0.3 if it matters?
  10. Well fiddlesticks lol Thanks man :-). I may brave upgrading in a few days… no rush for me lol. I’m good enough at breaking stuff. Still never got Collabora upgraded to new version. Need to try and find time to mess with that again. Oof lol
  11. This should be mostly relevant mate: For some of the other issues not covered by video search this this progress for errors; they’ve been heavily discussed. :-) Skois, today there is a update for MariaDB; are you suggesting I don’t try to roll forward to new version? I know yesterday you mentioned new MariaDB maybe having issues with NC but…?
  12. FWIW: Knock on wood no issues here with NC 21.0.3 and latest Linuxserver MariaDB…obviously I’m not the authority on it but
  13. All I can manage to get is 403 error. FWIW here is my proxy CONF file. Hastaged stuff is just different ways I was trying things. Not sure what to but UGGGHHH lol server { listen 443 ssl http2; server_name up.WAFFLES.NET; include /config/nginx/ssl.conf; #ssl_certificate /config/keys/cert.crt; #ssl_certificate_key /config/keys/cert.key; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; set $upstream_UptimeKuma UptimeKuma; #set $upstream_host 192.168.1.5; #set $upstream_port 3001; #set $upstream_proto https; proxy_pass http://192.168.1.5:3001; #proxy_pass $upstream_proto://$upstream_host:$upstream_port; proxy_http_version 1.1; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } Any ideas; any at all? Have tried forwarding as HTTP and HTTPS to no avail.
  14. I have a convoluted mess over here; doing some split DNS with HAPROXY on pfSense and Swag is a part of my disaster currently lol. I need to simplify everything. Maybe this is the que
  15. Ok, been fiddling with it all evening… Can someone share their redacted SWAG proxy conf file for using this with reverse proxy? Tried to modify sample provided on GitHub to no avail.
  16. Played with it more; still no dice [emoji22]. I’m sure it’s fail on my part just don’t know what
  17. Downgrade 6.4.9.3 and instantly works… log last night makes me wonder if it isn’t something with certificate verification box? Never had issue 6.4.9.3 before though or had to toggle that [emoji51] I can’t get 6.4.10.6 to work though
  18. Will try in AM. On my way to bed at current. Maybe I broke something else; albeit I haven’t been muckin in things LOL Thank you, Skois
  19. Doesn’t appear to be working here unless I’ve broken something else. Just restarted Nextcloud and Collabora so will try again in a sec. just sits on connecting.
  20. So it’s safe to remove “collabora/code:6.4.9.3” and go back to “collabora/code”? Thanks a ton mate!
  21. Yeah, not sure what they’ve got going on over there. Literally only use Mongo for RocketChat and I can barely keep it going for that lol
  22. Yeah for RocketChat here I had to “lock onto” “mongo:4.4.7”
  23. The gateway you created in pfsense for Unraid; what “interface” would that be? Can you share your gateway info for Unraid from pfSense, please?
  24. Comment out the “proxy_redirect” line in the OnlyOffice CONF. Restart Swag. Profit.