Blank white page after launcher rebuild app due to IP access

Hello,
I had to update the SMTP address so updated the same in app.yml and did a “ ./launcher rebuild app”. As part of that it updated all the packages and upon completion I am only able to to a blank white page.
I followed the suggestion given here (Blank white page after update) to set the version to stable, still no change. Can you please let me know what I should check? Below are the trailing logs from the rebuild command.

> I, [2020-08-20T06:10:08.607786 #1]  INFO -- : Replacing (?-mix:location @discourse {) with location @discourse {
>   limit_conn connperip $conn_per_ip;
>   limit_req zone=flood burst=$burst_per_second nodelay;
>   limit_req zone=bot burst=$burst_per_minute nodelay; in /etc/nginx/conf.d/discourse.conf
> I, [2020-08-20T06:10:08.608166 #1]  INFO -- : > echo "Beginning of custom commands"
> I, [2020-08-20T06:10:08.610509 #1]  INFO -- : Beginning of custom commands
> 
> I, [2020-08-20T06:10:08.610614 #1]  INFO -- : > echo "End of custom commands"
> I, [2020-08-20T06:10:08.612635 #1]  INFO -- : End of custom commands
> 
> I, [2020-08-20T06:10:08.612700 #1]  INFO -- : Terminating async processes
> I, [2020-08-20T06:10:08.612731 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/12/bin/postmaster -D /etc/postgresql/12/main pid: 52
> I, [2020-08-20T06:10:08.612779 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 169
> 2020-08-20 06:10:08.612 UTC [52] LOG:  received fast shutdown request
> 169:signal-handler (1597903808) Received SIGTERM scheduling shutdown...
> 2020-08-20 06:10:08.613 UTC [52] LOG:  aborting any active transactions
> 2020-08-20 06:10:08.616 UTC [52] LOG:  background worker "logical replication launcher" (PID 61) exited with exit code 1
> 2020-08-20 06:10:08.616 UTC [56] LOG:  shutting down
> 169:M 20 Aug 2020 06:10:08.619 # User requested shutdown...
> 169:M 20 Aug 2020 06:10:08.619 * Saving the final RDB snapshot before exiting.
> 169:M 20 Aug 2020 06:10:08.626 * DB saved on disk
> 169:M 20 Aug 2020 06:10:08.626 # Redis is now ready to exit, bye bye...
> 2020-08-20 06:10:08.672 UTC [52] LOG:  database system is shut down
> sha256:e4251470b644b45283a690923f0af6e59431606d9d18aceba110f18f6d9505fe
> 84717a9f5e214562e8dc82e0687956664c63e6cf1e3426cc0e77d9ac75868fe0
> Removing old container
> + /usr/bin/docker rm app
> app
> 
> + /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=8 -e UNICORN_SIDEKIQS=1 -e RUBY_GLOBAL_METHOD_CACHE_SIZE=131072 -e RUBY_GC_HEAP_GROWTH_MAX_SLOTS=40000 -e RUBY_GC_HEAP_INIT_SLOTS=400000 -e RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.5 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e DISCOURSE_HOSTNAME=forum.xxxxxx -e DISCOURSE_DEVELOPER_EMAILS=xxxxxxxxx@xxxxxxxxx,xxxxxxxxxx@xxxxxxxxx -e DISCOURSE_SMTP_ADDRESS=smtp.xxxxxxxxxx -e DISCOURSE_SMTP_PORT=25 -e DISCOURSE_SMTP_USER_NAME= -e DISCOURSE_SMTP_PASSWORD= -h NSC-QC-app -e DOCKER_HOST_IP=172.18.0.1 --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:1a:8e:9a:ec:3f local_discourse/app /sbin/boot
> 5925dc54b25648e07845933eea36ca31e9f141e4531195657c240e5799ceaaee

Logs from production.log:
> Started GET "/admin/site_settings/category/all_results?filter=mail" for 127.0.0.1 at 2020-08-20 06:58:03 +0000
> Processing by Admin::SiteSettingsController#index as HTML
>   Parameters: {"filter"=>"mail", "id"=>"all_results"}
>   Rendering default/empty.html.erb within layouts/application
>   Rendered default/empty.html.erb within layouts/application (Duration: 0.1ms | Allocations: 26)
>   Rendered layouts/_head.html.erb (Duration: 1.8ms | Allocations: 877)
>   Rendered common/_discourse_stylesheet.html.erb (Duration: 0.4ms | Allocations: 264)
>   Rendered application/_header.html.erb (Duration: 0.2ms | Allocations: 92)
> Completed 200 OK in 73ms (Views: 9.2ms | ActiveRecord: 0.0ms | Allocations: 33388)

Edit: If I use the curl command, then I can see the page being returned.
1 Like

see errors in the browser console, maybe some js-code causes an error and the page does not load

Found that the issue exists only while accessing using IP. Since there are some ongoing network changes, didn’t have a valid DNS name to access. After finding one hostname that resolves, the page is now loading.
Is there any limitation that access can only be through hostname?

1 Like

Yes, Discourse does not support being loaded at an IP address.

2 Likes