Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Collabora Online (CODE)
  3. Collabora Online stops working after restart (502 Bad Gateway)

Collabora Online stops working after restart (502 Bad Gateway)

Scheduled Pinned Locked Moved Solved Collabora Online (CODE)
24 Posts 4 Posters 2.3k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #14

    very strange that I cannot reproduce this anywhere. Can't see why it would try to load some private key in the first place. Did you tweak any of the configs?

    archosA 1 Reply Last reply
    0
    • nebulonN nebulon

      very strange that I cannot reproduce this anywhere. Can't see why it would try to load some private key in the first place. Did you tweak any of the configs?

      archosA Offline
      archosA Offline
      archos
      wrote on last edited by
      #15

      @nebulon No, I haven’t manually modified any configuration files. Everything was set up through the Cloudron interface.

      I have tried reinstalling Collabora multiple times, even on a different domain, but the issue persists. After installation, it works fine, but after a restart, it stops responding.

      The only changes I made were increasing the memory allocation and connecting multiple Nextcloud instances.

      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #16

        I have tried to reproduce this with two nextcloud instances having office documents open and restarting collabora various times. Unfortunately I cannot reproduce any of those bits. Are you able to reproduce this on the demo cloudron?

        archosA 1 Reply Last reply
        0
        • nebulonN nebulon

          I have tried to reproduce this with two nextcloud instances having office documents open and restarting collabora various times. Unfortunately I cannot reproduce any of those bits. Are you able to reproduce this on the demo cloudron?

          archosA Offline
          archosA Offline
          archos
          wrote on last edited by
          #17

          @nebulon Hi,
          I tried the demo instance of Collabora, but after a restart, I get the same error. I must be doing something wrong, but I really don't know what.

          I logged into Collabora and added my two Nextcloud domains: app1.demo.cloudron.io|app2.demo.cloudron.io. After a restart, I can no longer connect.

          At least now we know that the issue is somewhere on my side.

          1 Reply Last reply
          0
          • archosA Offline
            archosA Offline
            archos
            wrote on last edited by
            #18

            I also tried a fresh Nextcloud installation. My first Nextcloud instance is on the main domain, so I thought that might be the issue, but even with the new instance I have the same problem.

            After restarting the Collabora app, the same error appears again.

            It seems like someone had a similar issue here

            1 Reply Last reply
            0
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote on last edited by
              #19

              Aha, so possibly then changing the domain from default could be causing the issue. I didn't attempt that, since the test nextcloud instances are on the same main domain. Lets see if I can then reproduce it...

              1 Reply Last reply
              1
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #20

                I can now reproduce this by setting explicit domains. We have to debug and hopefully fix the package then. For the time being whildcard subdomains curiously seem to work fine as a workaround.

                M 1 Reply Last reply
                2
                • nebulonN nebulon

                  I can now reproduce this by setting explicit domains. We have to debug and hopefully fix the package then. For the time being whildcard subdomains curiously seem to work fine as a workaround.

                  M Offline
                  M Offline
                  msbt
                  App Dev
                  wrote on last edited by
                  #21

                  @nebulon can you also test it it multiple domains? I remember having issues with that a while back

                  1 Reply Last reply
                  1
                  • jdaviescoatesJ jdaviescoates referenced this topic on
                  • nebulonN Offline
                    nebulonN Offline
                    nebulon
                    Staff
                    wrote on last edited by
                    #22

                    We've pushed a new app package. If collabora is broken in your case, just delete the file coolwsd.xml via the cloudron filemanager and restart the app. Then reconfigure if needed via its configure form.

                    archosA 1 Reply Last reply
                    2
                    • nebulonN nebulon

                      We've pushed a new app package. If collabora is broken in your case, just delete the file coolwsd.xml via the cloudron filemanager and restart the app. Then reconfigure if needed via its configure form.

                      archosA Offline
                      archosA Offline
                      archos
                      wrote on last edited by
                      #23

                      @nebulon Wow, everything is working now! Thank you so much for your time and for fixing the app. 🙏

                      Just a quick question – for connecting a Nextcloud instance running on a different server, is it enough to just add the IP address of the server where Collabora is running to the WOPI allow list?

                      1 Reply Last reply
                      1
                      • nebulonN Offline
                        nebulonN Offline
                        nebulon
                        Staff
                        wrote on last edited by
                        #24

                        As far as I understand the domain will be verified with WOPI so probably add that, but then again I guess just give it a try.

                        1 Reply Last reply
                        1
                        • nebulonN nebulon marked this topic as a question on
                        • nebulonN nebulon has marked this topic as solved on
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Bookmarks
                        • Search