Rebuilding a fresh Discourse install pre-Ember 5 (targeting the beta channel), I am presented with an endless loading screen

installation
1

See title. I am in a bit of a pickle now. I am trying to roll back to a pre-Ember 5 build of Discourse to maintain legacy long term service support for my forum, which relies on plugins that have now been rendered inoperable under the new Discourse release. To roll back the clock by a few days, I have cleared everything away (destroyed the container and blew away /var/discourse and repulled from GitHub) and I am starting afresh with a pristine Discourse installation. In my .yml, I have specified “version: beta” so I should be pre-Ember 5.

After I do the usual of setting up my admin account and verifying it, I am presented with an endless loading screen. And yes, I also go into safe mode view and enable Force HTTPS as I always do with my setup.

image
image2880Ă—1754 270 KB

I have even tried every which way, removing plugins, and even starting afresh with no plugins except the absolute minimum of just…

      - git clone https://github.com/discourse/docker_manager.git

… in my .yml file. No dice. After setting up my admin account, I am still (barebones pristine install) presented with an endless loading screen of death.

Looking at the console, this is what I am seeing currently:

image
image2878Ă—1744 246 KB

Here is my current .yml file:

## this is the all-in-one, standalone Discourse Docker container template
##
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
##
## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
  #- "templates/web.ssl.template.yml"
  #- "templates/web.letsencrypt.ssl.template.yml"

## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see https://meta.discourse.org/t/17247 for details
expose:
  - "10080:80"   # http
  - "10443:443" # https

params:
  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can override
  db_shared_buffers: "2048MB"

  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)
  version: beta

  ## Maximum upload size (default: 10m)
  upload_size: 8196m

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override
  UNICORN_WORKERS: 8

  ## TODO: The domain name this Discourse instance will respond to
  ## Required. Discourse will not work with a bare IP number.
  DISCOURSE_HOSTNAME: forum.tabletpc.review

  ## Uncomment if you want the container to be started with the same
  ## hostname (-h option) as specified above (default "$hostname-$config")
  #DOCKER_USE_HOSTNAME: true

  ## TODO: List of comma delimited emails that will be made admin and developer
  ## on initial signup example 'user1@example.com,user2@example.com'
  DISCOURSE_DEVELOPER_EMAILS: 'admin@tabletpc.review'

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  # SMTP ADDRESS, username, and password are required
  # WARNING the char '#' in SMTP password can cause problems!
  DISCOURSE_SMTP_ADDRESS:  [REDACTED]
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME:  [REDACTED]
  DISCOURSE_SMTP_PASSWORD: " [REDACTED]"
  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)

  ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
  #LETSENCRYPT_ACCOUNT_EMAIL: me@example.com

  ## The CDN address for this Discourse instance (configured to pull)
  ## see https://meta.discourse.org/t/14857 for details
  #DISCOURSE_CDN_URL: //discourse-cdn.example.com

  DISCOURSE_MAXMIND_LICENSE_KEY: [REDACTED]

## The Docker container is stateless; all data is stored in /shared
volumes:
  - volume:
      host: /var/discourse/shared/tabletpcreview
      guest: /shared
  - volume:
      host: /var/discourse/shared/tabletpcreview/log/var-log
      guest: /var/log

## Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git

## Any custom commands to run after building
run:
  - exec: echo "Beginning of custom commands"
  ## If you want to set the 'From' email address for your first registration, uncomment and change:
  ## After getting the first signup email, re-comment the line. It only needs to run once.
  #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
  - exec: echo "End of custom commands"

EDIT: Oddly enough, if I disable plugins in safe mode, the site works. However, if I leave them enabled, it does not. My only plugin is Docker Manager, so why is it failing to load?

This works: https://forum.tabletpc.review/?safe_mode=no_plugins

This does not work: https://forum.tabletpc.review/?safe_mode=no_themes

3

Right, except right now, I have a clean install with literally nothing on it and the site refuses to load. See the .yml. No plugins. Also, no themes. No theme components. I am setting up from square one and getting the infinite loading screen. No plugins except the Docker Manager. I’m extremely confused why this is not working.

1 Like
4

OK, yes, sorry, that is confusing!

1 Like
5

So I think you should probably forget beta and switch to tests-passed to see if you can recover a build, then build it back piece by piece.

2 Likes
6

Indeed. I am going to try doing a fresh install in another environment. It seems beta is broken at the moment. In the past, I could target beta in my .yml. I am guessing that there is a breaking change in the Docker Manager plugin that is not backwards compatible.

1 Like
7

That did it. There must be a breaking change in Docker Manager that breaks beta. (Therefore, a warning to anyone on beta as their main container target to not upgrade!)

I’m whittling through and I think I have a good idea which plugin is culprit for mainline / tests-passed.

1 Like
8

Verdict: For those like me hanging on to it, with Ember 5, Retort is now dead. :frowning: Looking into options to preserve its features.

1 Like