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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Discourse
  3. ==> Migrating database fatal: not a git repository

==> Migrating database fatal: not a git repository

Scheduled Pinned Locked Moved Solved Discourse
14 Posts 4 Posters 4.1k Views 5 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.
  • rmdesR rmdes

    Anyone had any issue with Discourse ?

    I have a Discourse container that I can't get running again since last upgrade
    Logs :
    https://paste.armada.digital/okalicopuv.apache

    nebulonN Away
    nebulonN Away
    nebulon
    Staff
    wrote on last edited by
    #2

    @rmdes that error message about the git repository is to be expected, so looks like you hit some other issue. Is this a new installation or from an update?

    rmdesR 1 Reply Last reply
    0
    • rmdesR rmdes

      Anyone had any issue with Discourse ?

      I have a Discourse container that I can't get running again since last upgrade
      Logs :
      https://paste.armada.digital/okalicopuv.apache

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #3

      @rmdes is this from package 1.7.0 to 1.7.1 ?

      1 Reply Last reply
      0
      • nebulonN nebulon

        @rmdes that error message about the git repository is to be expected, so looks like you hit some other issue. Is this a new installation or from an update?

        rmdesR Offline
        rmdesR Offline
        rmdes
        wrote on last edited by rmdes
        #4

        @nebulon This is a long time running Discourse forum we have, this is after the upgrade.

        @girish org.discourse.cloudronapp@1.7.1

        girishG 1 Reply Last reply
        0
        • rmdesR rmdes

          @nebulon This is a long time running Discourse forum we have, this is after the upgrade.

          @girish org.discourse.cloudronapp@1.7.1

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #5

          @rmdes per the logs, discourse itself is starting fine. Something else is going wrong. Do you see any errors in /run/discourse/log ? I can also look into it if you write to us at support@cloudron.io

          rmdesR 1 Reply Last reply
          0
          • A Offline
            A Offline
            ari
            wrote on last edited by
            #6

            @girish I ran into a similar issue. I'll send over what I'm seeing in the production log via email.

            girishG 1 Reply Last reply
            0
            • A ari

              @girish I ran into a similar issue. I'll send over what I'm seeing in the production log via email.

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #7

              @ari From the logs, I see the below:

              Discourse::Deprecation (Deprecation notice: use_admin_ip_whitelist is deprecated, use the use_admin_ip_allowlist. (removal in Discourse 2.6)
              

              Can you use the File manager to edit site_settings.yml and rename that variable ? Is that variable even listed there?

              I am not sure why you see this error now since Discourse has not been updated in a month.

              A 1 Reply Last reply
              0
              • girishG girish

                @rmdes per the logs, discourse itself is starting fine. Something else is going wrong. Do you see any errors in /run/discourse/log ? I can also look into it if you write to us at support@cloudron.io

                rmdesR Offline
                rmdesR Offline
                rmdes
                wrote on last edited by
                #8

                @girish Hard to find something at that location regarding the error but the cloudron container log
                have this : Mar 20 08:54:40 2022/03/20 07:54:40 [error] 64#64: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "domain.org"

                rmdesR girishG 2 Replies Last reply
                0
                • rmdesR rmdes

                  @girish Hard to find something at that location regarding the error but the cloudron container log
                  have this : Mar 20 08:54:40 2022/03/20 07:54:40 [error] 64#64: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "domain.org"

                  rmdesR Offline
                  rmdesR Offline
                  rmdes
                  wrote on last edited by
                  #9

                  /run/discourse/log/unicorn.stderr.log

                  Passing 'script' command to redis as is; administrative commands cannot be effectively namespaced and should be called on the redis connection directly; passthrough has been deprecated and will be removed in redis-namespace 2.0 (at /app/code/vendor/bundle/ruby/2.7.0/gems/sidekiq-6.3.1/lib/sidekiq/scheduled.rb:45:in `zpopbyscore')

                  /run/discourse/log/unicorn.stdout.log

                  Loading Sidekiq in process id 89
                  2022-03-20T07:55:12.418Z pid=89 tid=cex WARN:

                  WARNING: Your Redis instance will evict Sidekiq data under heavy load.
                  The 'noeviction' maxmemory policy is recommended (current policy: 'allkeys-lru').
                  See: https://github.com/mperham/sidekiq/wiki/Using-Redis#memory

                  Can't find any hint to help us here on the production.log file 😕

                  1 Reply Last reply
                  0
                  • girishG girish

                    @ari From the logs, I see the below:

                    Discourse::Deprecation (Deprecation notice: use_admin_ip_whitelist is deprecated, use the use_admin_ip_allowlist. (removal in Discourse 2.6)
                    

                    Can you use the File manager to edit site_settings.yml and rename that variable ? Is that variable even listed there?

                    I am not sure why you see this error now since Discourse has not been updated in a month.

                    A Offline
                    A Offline
                    ari
                    wrote on last edited by
                    #10

                    @girish The site broke a few weeks ago, so the delay was just on my end in looking into it. After hand-updating a long list of deprecated settings, the app starts again. For reference, here is the full list of changes that I needed to make in site_settings.yml:

                    use_admin_ip_whitelist => use_admin_ip_allowlist
                    email_domains_blacklist => blocked_email_domains
                    email_domains_whitelist => allowed_email_domains
                    unicode_username_character_whitelist => allowed_unicode_username_characters
                    user_website_domains_whitelist => allowed_user_website_domains
                    whitelisted_link_domains => allowed_link_domains
                    embed_whitelist_selector => allowed_embed_selectors
                    auto_generated_whitelist => auto_generated_allowlist
                    attachment_content_type_blacklist => blocked_attachment_content_types
                    SiteSetting.enable_sso => SiteSetting.enable_discourse_connect
                    attachment_filename_blacklist => blocked_attachment_filenames
                    blacklist_ip_blocks => blocked_ip_blocks
                    whitelist_internal_hosts => allowed_internal_hosts
                    whitelisted_crawler_user_agents => allowed_crawler_user_agents
                    blacklisted_crawler_user_agents => blocked_crawler_user_agents
                    onebox_domains_blacklist => blocked_onebox_domains
                    inline_onebox_domains_whitelist => allowed_inline_onebox_domains
                    white_listed_spam_host_domains => allowed_spam_host_domains
                    embed_blacklist_selector => blocked_embed_selectors
                    embed_classname_whitelist => allowed_embed_classnames
                    ---
                    SiteSetting.sso_overrides_email => SiteSetting.auth_overrides_email 
                    SiteSetting.sso_overrides_avatar => SiteSetting.discourse_connect_overrides_avatar
                    SiteSetting.enable_category_group_review => SiteSetting.enable_category_group_moderation
                    SiteSetting.newuser_max_images => SiteSetting.newuser_max_embedded_media
                    
                    1 Reply Last reply
                    1
                    • rmdesR rmdes

                      @girish Hard to find something at that location regarding the error but the cloudron container log
                      have this : Mar 20 08:54:40 2022/03/20 07:54:40 [error] 64#64: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "domain.org"

                      girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by
                      #11

                      @rmdes Are you able to find and Deprecation in the comments? I recommend restart the app to get the "fresh" logs, otherwise the Logs button sometimes shows stale logs.

                      rmdesR 1 Reply Last reply
                      0
                      • girishG girish

                        @rmdes Are you able to find and Deprecation in the comments? I recommend restart the app to get the "fresh" logs, otherwise the Logs button sometimes shows stale logs.

                        rmdesR Offline
                        rmdesR Offline
                        rmdes
                        wrote on last edited by
                        #12

                        @girish I don't understand the Deprecation part...

                        girishG 1 Reply Last reply
                        0
                        • rmdesR rmdes

                          @girish I don't understand the Deprecation part...

                          girishG Offline
                          girishG Offline
                          girish
                          Staff
                          wrote on last edited by
                          #13

                          @rmdes Can you drop us a mail at support@cloudron.io . I think we have to look into your app to investigate further.

                          1 Reply Last reply
                          1
                          • girishG Offline
                            girishG Offline
                            girish
                            Staff
                            wrote on last edited by
                            #14

                            Ah, it's similar issue. It's not clear from the logs because that file is not in the manifest, I have fixed the package now to show the error.

                            Processing by CategoriesController#index as HTML
                            Completed 500 Internal Server Error in 22ms (ActiveRecord: 0.0ms | Allocations: 1948)
                            Discourse::Deprecation (Deprecation notice: use_admin_ip_whitelist is deprecated, use the use_admin_ip_allowlist. (removal in Discourse 2.6) 
                            At /app/code/lib/site_setting_extension.rb:211:in `public_send`)
                            lib/discourse.rb:860:in `deprecate'
                            app/models/site_setting.rb:241:in `block (2 levels) in <class:SiteSetting>'
                            lib/site_setting_extension.rb:211:in `public_send'
                            lib/site_setting_extension.rb:211:in `block in client_settings_json_uncached'
                            lib/site_setting_extension.rb:210:in `map'
                            lib/site_setting_extension.rb:210:in `client_settings_json_uncached'
                            lib/site_setting_extension.rb:205:in `block in client_settings_json'
                            lib/cache.rb:94:in `fetch'
                            lib/site_setting_extension.rb:204:in `client_settings_json'
                            app/controllers/application_controller.rb:596:in `preload_anonymous_data'
                            app/controllers/application_controller.rb:407:in `preload_json'
                            app/controllers/application_controller.rb:387:in `block in with_resolved_locale'
                            app/controllers/application_controller.rb:387:in `with_resolved_locale'
                            lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
                            lib/content_security_policy/middleware.rb:12:in `call'
                            lib/middleware/anonymous_cache.rb:354:in `call'
                            config/initializers/100-quiet_logger.rb:23:in `call'
                            config/initializers/100-silence_logger.rb:31:in `call'
                            lib/middleware/enforce_hostname.rb:23:in `call'
                            lib/middleware/request_tracker.rb:198:in `call'
                            
                            1 Reply Last reply
                            0
                            • girishG girish has marked this topic as solved on

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            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