503 error nginx

joea · February 8, 2024, 5:46pm

I would need a bit more guidance on which logs. There are a number of named files and directories in /var/log. Most I’ve looked have no content.

Is there an existing document on what to provide?

docker-compose -ps is below:

joea · February 8, 2024, 7:12pm

The logs I have manged to scrape together are far, far, too large to be posted here. I know, I tried.

Do you have a preferred way to get these? Pastebin, or like that?

joea · February 8, 2024, 8:33pm

Oh. I guess you meant the the output of "docker-compose logs --tail=“all”. ?

Here then (in three parts):

joea@my-host:~ $ docker-compose logs --tail=“all”
Attaching to nginx-proxy-acme, grampsweb_celery, grampsweb, nginx-proxy, grampsweb_redis
grampsweb_redis | 1:C 08 Feb 2024 16:18:21.863 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
grampsweb_redis | 1:C 08 Feb 2024 16:18:21.863 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
grampsweb_redis | 1:C 08 Feb 2024 16:18:21.863 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
grampsweb_redis | 1:M 08 Feb 2024 16:18:21.864 * monotonic clock: POSIX clock_gettime
grampsweb_redis | 1:M 08 Feb 2024 16:18:21.866 * Running mode=standalone, port=6379.
grampsweb_redis | 1:M 08 Feb 2024 16:18:21.867 * Server initialized
grampsweb_redis | 1:M 08 Feb 2024 16:18:21.868 * Ready to accept connections tcp
grampsweb_redis | 1:M 08 Feb 2024 17:18:22.030 * 1 changes in 3600 seconds. Saving…
grampsweb_redis | 1:M 08 Feb 2024 17:18:22.031 * Background saving started by pid 23
grampsweb_redis | 23:C 08 Feb 2024 17:18:22.043 * DB saved on disk
grampsweb_redis | 23:C 08 Feb 2024 17:18:22.044 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
grampsweb_redis | 1:M 08 Feb 2024 17:18:22.132 * Background saving terminated with success
grampsweb_redis | 1:M 08 Feb 2024 18:18:23.065 * 1 changes in 3600 seconds. Saving…
grampsweb_redis | 1:M 08 Feb 2024 18:18:23.068 * Background saving started by pid 24
grampsweb_redis | 24:C 08 Feb 2024 18:18:23.080 * DB saved on disk
grampsweb_redis | 24:C 08 Feb 2024 18:18:23.081 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
grampsweb_redis | 1:M 08 Feb 2024 18:18:23.169 * Background saving terminated with success
grampsweb_redis | 1:M 08 Feb 2024 19:18:24.011 * 1 changes in 3600 seconds. Saving…
grampsweb_redis | 1:M 08 Feb 2024 19:18:24.012 * Background saving started by pid 38
grampsweb_redis | 38:C 08 Feb 2024 19:18:24.025 * DB saved on disk
grampsweb_redis | 38:C 08 Feb 2024 19:18:24.027 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
grampsweb_redis | 1:M 08 Feb 2024 19:18:24.114 * Background saving terminated with success
grampsweb_redis | 1:M 08 Feb 2024 20:18:25.064 * 1 changes in 3600 seconds. Saving…
grampsweb_redis | 1:M 08 Feb 2024 20:18:25.065 * Background saving started by pid 39
grampsweb_redis | 39:C 08 Feb 2024 20:18:25.076 * DB saved on disk
grampsweb_redis | 39:C 08 Feb 2024 20:18:25.077 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
grampsweb_redis | 1:M 08 Feb 2024 20:18:25.166 * Background saving terminated with success
grampsweb_celery |
grampsweb_celery | (main.py:10): Gtk-CRITICAL **: 16:18:31.626: gtk_icon_theme_get_for_screen: assertion ‘GDK_IS_SCREEN (screen)’ failed
grampsweb_celery | INFO:gramps_webapi:Rebuilding search index …
grampsweb_celery | Traceback (most recent call last):
grampsweb_celery | File “”, line 198, in _run_module_as_main
grampsweb_celery | File “”, line 88, in _run_code
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/main.py”, line 202, in
grampsweb_celery | cli(
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1157, in call
grampsweb_celery | return self.main(*args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1078, in main
grampsweb_celery | rv = self.invoke(ctx)
grampsweb_celery | ^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1688, in invoke
grampsweb_celery | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1688, in invoke
grampsweb_celery | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1434, in invoke
grampsweb_celery | return ctx.invoke(self.callback, **ctx.params)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 783, in invoke
grampsweb_celery | return __callback(*args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/decorators.py”, line 33, in new_func
grampsweb_celery | return f(get_current_context(), *args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/main.py”, line 149, in index_full
grampsweb_celery | db = db_manager.get_db().db
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/dbmanager.py”, line 177, in get_db
grampsweb_celery | smgr.open_activate(
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/dbloader.py”, line 119, in open_activate
grampsweb_celery | self.read_file(filename, mode, username, password)
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/dbloader.py”, line 98, in read_file
grampsweb_celery | self.dbstate.db.load(
grampsweb_celery | File “/usr/lib/python3/dist-packages/gramps/gen/db/generic.py”, line 597, in load
grampsweb_celery | self._create_schema()
grampsweb_celery | File “/usr/lib/python3/dist-packages/gramps/plugins/db/dbapi/dbapi.py”, line 75, in _create_schema
grampsweb_celery | self.dbapi.execute('CREATE TABLE person ’
grampsweb_celery | File “/usr/lib/python3/dist-packages/gramps/plugins/db/dbapi/sqlite.py”, line 133, in execute
grampsweb_celery | self.__cursor.execute(*args, **kwargs)
grampsweb_celery | sqlite3.OperationalError: table person already exists
grampsweb_celery | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
grampsweb_celery | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
grampsweb_celery | /usr/local/lib/python3.11/dist-packages/celery/platforms.py:829: SecurityWarning: You’re running the worker with superuser privileges: this is
grampsweb_celery | absolutely not recommended!
grampsweb_celery |
grampsweb_celery | Please specify a different user using the --uid option.
grampsweb_celery |
grampsweb_celery | User information: uid=0 euid=0 gid=0 egid=0
grampsweb_celery |
grampsweb_celery | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format(
grampsweb_celery |
grampsweb_celery | -------------- celery@39af58421f10 v5.3.6 (emerald-rush)
grampsweb_celery | — ***** -----
grampsweb_celery | – ******* ---- Linux-6.1.0-rpi8-rpi-v8-aarch64-with-glibc2.36 2024-02-08 16:18:55
grampsweb |
grampsweb | (main.py:12): Gtk-CRITICAL **: 16:18:31.626: gtk_icon_theme_get_for_screen: assertion ‘GDK_IS_SCREEN (screen)’ failed
grampsweb | INFO:gramps_webapi:Rebuilding search index …
grampsweb | INFO:gramps_webapi:Done building search index.
grampsweb | INFO [alembic.runtime.migration] Context impl SQLiteImpl.
grampsweb | INFO [alembic.runtime.migration] Will assume non-transactional DDL.
grampsweb | INFO [alembic.runtime.migration] Running upgrade → c89728e71264, empty message
grampsweb | INFO [alembic.runtime.migration] Running upgrade c89728e71264 → e5e738d09fa7, Added configuration table
grampsweb | INFO [alembic.runtime.migration] Running upgrade e5e738d09fa7 → e176543c72a8, Add tree column to User
grampsweb | INFO [alembic.runtime.migration] Running upgrade e176543c72a8 → 66e56620891a, Add trees table
grampsweb | INFO [alembic.runtime.migration] Running upgrade 66e56620891a → 22c8d1fba959, Add trees.enabled
grampsweb | INFO [alembic.runtime.migration] Running upgrade 22c8d1fba959 → b0582f54029c, Use BigInt for usage_media
grampsweb | INFO [alembic.runtime.migration] Running upgrade b0582f54029c → 84960b7d968c, Use BigInt for quota_media
grampsweb | [2024-02-08 16:18:45 +0000] [18] [INFO] Starting gunicorn 21.2.0
grampsweb | [2024-02-08 16:18:45 +0000] [18] [INFO] Listening at: http://0.0.0.0:5000 (18)
grampsweb | [2024-02-08 16:18:45 +0000] [18] [INFO] Using worker: sync
grampsweb | [2024-02-08 16:18:45 +0000] [19] [INFO] Booting worker with pid: 19
grampsweb | [2024-02-08 16:18:45 +0000] [20] [INFO] Booting worker with pid: 20
grampsweb | [2024-02-08 16:18:45 +0000] [21] [INFO] Booting worker with pid: 21
grampsweb | [2024-02-08 16:18:45 +0000] [22] [INFO] Booting worker with pid: 22
grampsweb | [2024-02-08 16:18:45 +0000] [23] [INFO] Booting worker with pid: 23
grampsweb | [2024-02-08 16:18:46 +0000] [24] [INFO] Booting worker with pid: 24
grampsweb | [2024-02-08 16:18:46 +0000] [25] [INFO] Booting worker with pid: 25
grampsweb | [2024-02-08 16:18:46 +0000] [26] [INFO] Booting worker with pid: 26
grampsweb_celery | - *** — * —
grampsweb_celery | - ** ---------- [config]
grampsweb_celery | - ** ---------- .> app: default:0x7fad4cf5d0 (.default.Loader)
grampsweb_celery | - ** ---------- .> transport: redis://grampsweb_redis:6379/0
grampsweb_celery | - ** ---------- .> results: redis://grampsweb_redis:6379/0
grampsweb_celery | - *** — * — .> concurrency: 4 (prefork)
grampsweb_celery | – ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
grampsweb_celery | — ***** -----
grampsweb_celery | -------------- [queues]
grampsweb_celery | .> celery exchange=celery(direct) key=celery
grampsweb_celery |
grampsweb_celery |
grampsweb_celery | [tasks]
grampsweb_celery | . gramps_webapi.api.tasks.export_db
grampsweb_celery | . gramps_webapi.api.tasks.export_media
grampsweb_celery | . gramps_webapi.api.tasks.generate_report
grampsweb_celery | . gramps_webapi.api.tasks.import_file
grampsweb_celery | . gramps_webapi.api.tasks.import_media_archive
grampsweb_celery | . gramps_webapi.api.tasks.media_ocr
grampsweb_celery | . gramps_webapi.api.tasks.search_reindex_full
grampsweb_celery | . gramps_webapi.api.tasks.search_reindex_incremental
grampsweb_celery | . gramps_webapi.api.tasks.send_email_confirm_email
grampsweb_celery | . gramps_webapi.api.tasks.send_email_new_user
grampsweb_celery | . gramps_webapi.api.tasks.send_email_reset_password
grampsweb_celery |
grampsweb_celery | [2024-02-08 16:18:57,006: WARNING/MainProcess] /usr/local/lib/python3.11/dist-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
grampsweb_celery | whether broker connection retries are made during startup in Celery 6.0 and above.
grampsweb_celery | If you wish to retain the existing behavior for retrying connections on startup,
grampsweb_celery | you should set broker_connection_retry_on_startup to True.
grampsweb_celery | warnings.warn(
grampsweb_celery |
grampsweb_celery | [2024-02-08 16:18:57,070: INFO/MainProcess] Connected to redis://grampsweb_redis:6379/0
grampsweb_celery | [2024-02-08 16:18:57,075: WARNING/MainProcess] /usr/local/lib/python3.11/dist-packages/celery/worker/consumer/consumer.py:507: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
grampsweb_celery | whether broker connection retries are made during startup in Celery 6.0 and above.
grampsweb_celery | If you wish to retain the existing behavior for retrying connections on startup,
grampsweb_celery | you should set broker_connection_retry_on_startup to True.
grampsweb_celery | warnings.warn(
grampsweb_celery |
grampsweb_celery | [2024-02-08 16:18:57,097: INFO/MainProcess] mingle: searching for neighbors
grampsweb_celery | [2024-02-08 16:18:58,138: INFO/MainProcess] mingle: all alone
grampsweb_celery | [2024-02-08 16:18:58,200: INFO/MainProcess] celery@39af58421f10 ready.

joea · February 8, 2024, 8:35pm

Part II -
nginx-proxy-acme | Info: running acme-companion version v2.2.10-9-g02fad92
nginx-proxy | Info: running nginx-proxy version 1.4.0-75-g3d61f47
nginx-proxy | Setting up DH Parameters…
nginx-proxy | Warning: TRUST_DOWNSTREAM_PROXY is not set; defaulting to “true”. For security, you should explicitly set TRUST_DOWNSTREAM_PROXY to “false” if there is not a trusted reverse proxy in front of this proxy.
nginx-proxy | Warning: The default value of TRUST_DOWNSTREAM_PROXY might change to “false” in a future version of nginx-proxy. If you require TRUST_DOWNSTREAM_PROXY to be enabled, explicitly set it to “true”.
nginx-proxy | forego | starting dockergen.1 on port 5000
nginx-proxy | forego | starting nginx.1 on port 5100
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: using the “epoll” event method
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: nginx/1.25.3
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: built by gcc 12.2.0 (Debian 12.2.0-14)
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: OS: Linux 6.1.0-rpi8-rpi-v8
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: getrlimit(RLIMIT_NOFILE): 1048576:1048576
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker processes
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 28
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 29
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 30
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 31
nginx-proxy | dockergen.1 | 2024/02/08 16:18:22 Error inspecting container: 39af58421f103d7680960fef9a37a3379cdabf55c90919e8934b6f9486477afb: No such container: 39af58421f103d7680960fef9a37a3379cdabf55c90919e8934b6f9486477afb
nginx-proxy | dockergen.1 | 2024/02/08 16:18:22 Generated ‘/etc/nginx/conf.d/default.conf’ from 3 containers
nginx-proxy | dockergen.1 | 2024/02/08 16:18:22 Running ‘nginx -s reload’
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 1 (SIGHUP) received from 33, reconfiguring
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: reconfiguring
nginx-proxy | dockergen.1 | 2024/02/08 16:18:22 Watching docker events
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: using the “epoll” event method
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker processes
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 38
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 39
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 40
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: start worker process 41
nginx-proxy | dockergen.1 | 2024/02/08 16:18:22 Error inspecting container: 54c2ac288f2107caf03463db9a7ebf78db96c54b3310fa4ebbfd93250b822753: No such container: 54c2ac288f2107caf03463db9a7ebf78db96c54b3310fa4ebbfd93250b822753
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 30#30: gracefully shutting down
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 31#31: gracefully shutting down
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 30#30: exiting
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 31#31: exiting
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 30#30: exit
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 28#28: gracefully shutting down
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 29#29: gracefully shutting down
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 31#31: exit
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 29#29: exiting
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 29#29: exit
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 28#28: exiting
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 28#28: exit
nginx-proxy | dockergen.1 | 2024/02/08 16:18:22 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘nginx -s reload’
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 17 (SIGCHLD) received from 31
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: worker process 31 exited with code 0
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 29 (SIGIO) received
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 17 (SIGCHLD) received from 29
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: worker process 29 exited with code 0
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 29 (SIGIO) received
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 17 (SIGCHLD) received from 30
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: worker process 30 exited with code 0
nginx-proxy-acme | …+…+…+…+…+…+…+…+…+++++++++++++++++++++++++++++++++++++++++++++…+…+…+…+…+…+…+…+.+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+.+…+…+.+…+…+…+++++++++++++++++++++++++++++++++++++++++++++…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+.+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+.+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+.+…+.+…+.+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+.+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+.+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+.+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+.+…+…+…+…+.+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+.+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+.+…+…+…+…+.+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+.+…+…+…+…+.+…+.+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+.+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+++++
nginx-proxy-acme | …+++++++++++++++++++++++++++++++++++++++++++++…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+++++++++++++++++++++++++++++++++++++++++++++…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+.+…+…+…+.+…+…+…+…+…+.+…+…+…+…+…+…+.+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+.+…+…+…+…+…+…+.+…+.+…+…+…+.+…+…+…+.+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+.+…+…+…+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+…+…+…+…+…+.+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+…+.+++++
nginx-proxy-acme | -----
nginx-proxy-acme | Reloading nginx proxy (nginx-proxy)…
nginx-proxy-acme | 2024/02/08 16:18:54 Generated ‘/etc/nginx/conf.d/default.conf’ from 5 containers
nginx-proxy-acme | 2024/02/08 16:18:54 [notice] 53#53: signal process started
nginx-proxy-acme | Info: a default key and certificate have been created at /etc/nginx/certs/default.key and /etc/nginx/certs/default.crt.
nginx-proxy-acme | Info: Setting up 4096 bits RFC7919 Diffie-Hellman group…
nginx-proxy-acme | Reloading nginx proxy (nginx-proxy)…
nginx-proxy-acme | 2024/02/08 16:18:55 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘’
nginx-proxy-acme | 2024/02/08 16:18:55 [notice] 70#70: signal process started
nginx-proxy-acme | 2024/02/08 16:18:55 Generated ‘/app/letsencrypt_service_data’ from 5 containers
nginx-proxy-acme | 2024/02/08 16:18:55 Running ‘/app/signal_le_service’
nginx-proxy-acme | 2024/02/08 16:18:55 Watching docker events
nginx-proxy-acme | 2024/02/08 16:18:55 Contents of /app/letsencrypt_service_data did not change. Skipping notification ‘/app/signal_le_service’
nginx-proxy-acme | [Thu Feb 8 16:18:58 UTC 2024] Create account key ok.
nginx-proxy-acme | [Thu Feb 8 16:18:58 UTC 2024] Registering account: https://acme-v02.api.letsencrypt.org/directory
nginx-proxy-acme | [Thu Feb 8 16:19:00 UTC 2024] Registered
nginx-proxy-acme | [Thu Feb 8 16:19:00 UTC 2024] ACCOUNT_THUMBPRINT=‘9TZPFCosXhzD8d6Ecq91bCPUccJXd5OQnzwv9H2WQTQ’
nginx-proxy-acme | Reloading nginx proxy (nginx-proxy)…
nginx-proxy-acme | 2024/02/08 16:19:01 Generated ‘/etc/nginx/conf.d/default.conf’ from 5 containers
nginx-proxy-acme | 2024/02/08 16:19:01 [notice] 87#87: signal process started
nginx-proxy-acme | Creating/renewal www.my-domain.com certificates… (www.my-domain.com my-domain.com)
nginx-proxy-acme | [Thu Feb 8 16:19:03 UTC 2024] Using CA: https://acme-v02.api.letsencrypt.org/directory
nginx-proxy-acme | [Thu Feb 8 16:19:03 UTC 2024] Creating domain key
nginx-proxy-acme | [Thu Feb 8 16:19:08 UTC 2024] The domain key is here: /etc/acme.sh/joea@some-mail.com/www.my-domain.com/www.my-domain.com.key
nginx-proxy-acme | [Thu Feb 8 16:19:08 UTC 2024] Generate next pre-generate key.
nginx-proxy-acme | [Thu Feb 8 16:19:11 UTC 2024] Multi domain=‘DNS:www.my-domain.com,DNS:my-domain.com’
nginx-proxy-acme | [Thu Feb 8 16:19:11 UTC 2024] Getting domain auth token for each domain
nginx-proxy-acme | [Thu Feb 8 16:19:14 UTC 2024] Getting webroot for domain=‘www.my-domain.com’
nginx-proxy-acme | [Thu Feb 8 16:19:14 UTC 2024] Getting webroot for domain=‘my-domain.com’
nginx-proxy-acme | [Thu Feb 8 16:19:14 UTC 2024] Verifying: www.my-domain.com
nginx-proxy-acme | [Thu Feb 8 16:19:15 UTC 2024] Pending, The CA is processing your order, please just wait. (1/30)
nginx-proxy-acme | [Thu Feb 8 16:19:18 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/ei2wfvsu_woz5hTyVBhAlbRz7H35Ba7_soKmgxjtuR8:
nginx-proxy-acme | [Thu Feb 8 16:19:18 UTC 2024] Please check log file for more details: /dev/null
nginx-proxy-acme | Sleep for 3600s
nginx-proxy-acme | Creating/renewal www.my-domain.com certificates… (www.my-domain.com my-domain.com)
nginx-proxy-acme | [Thu Feb 8 17:19:21 UTC 2024] Using CA: https://acme-v02.api.letsencrypt.org/directory
nginx-proxy-acme | [Thu Feb 8 17:19:21 UTC 2024] Using pre generated key: /etc/acme.sh/joea@some-mail.com/www.my-domain.com/www.my-domain.com.key.next
nginx-proxy-acme | [Thu Feb 8 17:19:21 UTC 2024] Generate next pre-generate key.
nginx-proxy-acme | [Thu Feb 8 17:19:26 UTC 2024] Multi domain=‘DNS:www.my-domain.com,DNS:my-domain.com’
nginx-proxy-acme | [Thu Feb 8 17:19:26 UTC 2024] Getting domain auth token for each domain
nginx-proxy-acme | [Thu Feb 8 17:19:29 UTC 2024] Getting webroot for domain=‘www.my-domain.com’
nginx-proxy-acme | [Thu Feb 8 17:19:29 UTC 2024] Getting webroot for domain=‘my-domain.com’
nginx-proxy-acme | [Thu Feb 8 17:19:30 UTC 2024] Verifying: www.my-domain.com
nginx-proxy-acme | [Thu Feb 8 17:19:30 UTC 2024] Pending, The CA is processing your order, please just wait. (1/30)
nginx-proxy-acme | [Thu Feb 8 17:19:33 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/urh-MhcOYQ9vcmXbbP4KLWCE4jHv7MzkhcAP2v65K0U:
nginx-proxy-acme | [Thu Feb 8 17:19:33 UTC 2024] Please check log file for more details: /dev/null
nginx-proxy-acme | Sleep for 3600s
nginx-proxy-acme | Creating/renewal www.my-domain.com certificates… (www.my-domain.com my-domain.com)
nginx-proxy-acme | [Thu Feb 8 18:19:36 UTC 2024] Using CA: https://acme-v02.api.letsencrypt.org/directory
nginx-proxy-acme | [Thu Feb 8 18:19:36 UTC 2024] Using pre generated key: /etc/acme.sh/joea@some-mail.com/www.my-domain.com/www.my-domain.com.key.next
nginx-proxy-acme | [Thu Feb 8 18:19:36 UTC 2024] Generate next pre-generate key.
nginx-proxy-acme | [Thu Feb 8 18:19:37 UTC 2024] Multi domain=‘DNS:www.my-domain.com,DNS:my-domain.com’
nginx-proxy-acme | [Thu Feb 8 18:19:38 UTC 2024] Getting domain auth token for each domain
nginx-proxy | nginx.1 | 2024/02/08 16:18:22 [notice] 22#22: signal 29 (SIGIO) received
nginx-proxy | nginx.1 | 2024/02/08 16:18:23 [notice] 22#22: signal 17 (SIGCHLD) received from 28
nginx-proxy | nginx.1 | 2024/02/08 16:18:23 [notice] 22#22: worker process 28 exited with code 0
nginx-proxy | nginx.1 | 2024/02/08 16:18:23 [notice] 22#22: signal 29 (SIGIO) received
nginx-proxy | dockergen.1 | 2024/02/08 16:18:24 Received event start for container 54c2ac288f21
nginx-proxy | dockergen.1 | 2024/02/08 16:18:24 Received event start for container 39af58421f10
nginx-proxy | dockergen.1 | 2024/02/08 16:18:24 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘nginx -s reload’
nginx-proxy | dockergen.1 | 2024/02/08 16:18:24 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘nginx -s reload’
nginx-proxy | nginx.1 | 2024/02/08 16:18:31 [error] 38#38: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET /favicon.ico HTTP/1.1”, upstream: “http://172.20.0.3:5000/favicon.ico”, host: “www.my-domain.com”, referrer: “Give yourself a better website » MY DOMAIN”
nginx-proxy | nginx.1 | www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:31 +0000] “GET /favicon.ico HTTP/1.1” 502 157 “Give yourself a better website » MY DOMAIN” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
nginx-proxy | nginx.1 | 2024/02/08 16:18:31 [error] 38#38: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET /images/icon192.png HTTP/1.1”, upstream: “http://172.20.0.3:5000/images/icon192.png”, host: “www.my-domain.com”, referrer: “Give yourself a better website » MY DOMAIN”
nginx-proxy | nginx.1 | www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:31 +0000] “GET /images/icon192.png HTTP/1.1” 502 157 “Give yourself a better website » MY DOMAIN” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
nginx-proxy-acme | [Thu Feb 8 18:19:40 UTC 2024] Getting webroot for domain=‘www.my-domain.com’
nginx-proxy-acme | [Thu Feb 8 18:19:41 UTC 2024] Getting webroot for domain=‘my-domain.com’
nginx-proxy-acme | [Thu Feb 8 18:19:41 UTC 2024] Verifying: www.my-domain.com
nginx-proxy-acme | [Thu Feb 8 18:19:42 UTC 2024] Pending, The CA is processing your order, please just wait. (1/30)
nginx-proxy-acme | [Thu Feb 8 18:19:44 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/is4cn0rs7NPIMsAy04wMh24aBBu_2ufkwtZ4YmNriH8:
nginx-proxy-acme | [Thu Feb 8 18:19:45 UTC 2024] Please check log file for more details: /dev/null
nginx-proxy-acme | Sleep for 3600s
nginx-proxy-acme | Creating/renewal www.my-domain.com certificates… (www.my-domain.com my-domain.com)
nginx-proxy-acme | [Thu Feb 8 19:19:47 UTC 2024] Using CA: https://acme-v02.api.letsencrypt.org/directory
nginx-proxy-acme | [Thu Feb 8 19:19:48 UTC 2024] Using pre generated key: /etc/acme.sh/joea@some-mail.com/www.my-domain.com/www.my-domain.com.key.next
nginx-proxy-acme | [Thu Feb 8 19:19:48 UTC 2024] Generate next pre-generate key.
nginx-proxy-acme | [Thu Feb 8 19:19:50 UTC 2024] Multi domain=‘DNS:www.my-domain.com,DNS:my-domain.com’
nginx-proxy-acme | [Thu Feb 8 19:19:50 UTC 2024] Getting domain auth token for each domain
nginx-proxy-acme | [Thu Feb 8 19:19:53 UTC 2024] Getting webroot for domain=‘www.my-domain.com’
nginx-proxy-acme | [Thu Feb 8 19:19:53 UTC 2024] Getting webroot for domain=‘my-domain.com’
nginx-proxy-acme | [Thu Feb 8 19:19:53 UTC 2024] Verifying: www.my-domain.com
nginx-proxy-acme | [Thu Feb 8 19:19:54 UTC 2024] Pending, The CA is processing your order, please just wait. (1/30)
nginx-proxy-acme | [Thu Feb 8 19:19:57 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/vr1svzBJYO2I9ce6OdqW2g4cMCZkFS3DAXUEuMjG_tA:
nginx-proxy-acme | [Thu Feb 8 19:19:57 UTC 2024] Please check log file for more details: /dev/null
nginx-proxy-acme | Sleep for 3600s
nginx-proxy-acme | Creating/renewal www.my-domain.com certificates… (www.my-domain.com my-domain.com)
nginx-proxy-acme | [Thu Feb 8 20:19:59 UTC 2024] Using CA: https://acme-v02.api.letsencrypt.org/directory
nginx-proxy-acme | [Thu Feb 8 20:20:00 UTC 2024] Using pre generated key: /etc/acme.sh/joea@some-mail.com/www.my-domain.com/www.my-domain.com.key.next
nginx-proxy-acme | [Thu Feb 8 20:20:00 UTC 2024] Generate next pre-generate key.
nginx-proxy-acme | [Thu Feb 8 20:20:03 UTC 2024] Multi domain=‘DNS:www.my-domain.com,DNS:my-domain.com’
nginx-proxy-acme | [Thu Feb 8 20:20:03 UTC 2024] Getting domain auth token for each domain
nginx-proxy-acme | [Thu Feb 8 20:20:06 UTC 2024] Getting webroot for domain=‘www.my-domain.com’
nginx-proxy-acme | [Thu Feb 8 20:20:06 UTC 2024] Getting webroot for domain=‘my-domain.com’
nginx-proxy-acme | [Thu Feb 8 20:20:06 UTC 2024] Verifying: www.my-domain.com
nginx-proxy-acme | [Thu Feb 8 20:20:07 UTC 2024] Pending, The CA is processing your order, please just wait. (1/30)
nginx-proxy-acme | [Thu Feb 8 20:20:10 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/6_vZT2Scjrpz0t-1VgHKeUiGgOxhw8hqsX4vYA4UiKI: 503
nginx-proxy-acme | [Thu Feb 8 20:20:10 UTC 2024] Please check log file for more details: /dev/null
nginx-proxy-acme | Sleep for 3600s

joea · February 8, 2024, 8:36pm

Part III:

nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy nginx-proxy nginx-proxy nginx-proxy nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 nginx-proxy | nginx.1 joea@my-host:~ $ | 2024/02/08 16:18:31 [error] 39#39: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET /images/favicon.ico HTTP/1.1”, upstream: “http://172.20.0.3:5000/images/favicon.ico”, host: “www.my-domain.com”, referrer: “Give yourself a better website » MY DOMAIN”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:31 +0000] “GET /images/favicon.ico HTTP/1.1” 502 157 “Give yourself a better website » MY DOMAIN” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| dockergen.1 | 2024/02/08 16:18:33 Received event die for container 39af58421f10
| dockergen.1 | 2024/02/08 16:18:34 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘nginx -s reload’
| dockergen.1 | 2024/02/08 16:18:35 Received event start for container 39af58421f10
| dockergen.1 | 2024/02/08 16:18:35 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ‘nginx -s reload’
| 2024/02/08 16:18:37 [error] 38#38: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET /firstrun HTTP/1.1”, upstream: “http://172.20.0.3:5000/firstrun”, host: “www.my-domain.com”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:37 +0000] “GET /firstrun HTTP/1.1” 502 157 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| 2024/02/08 16:18:37 [error] 39#39: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET /favicon.ico HTTP/1.1”, upstream: “http://172.20.0.3:5000/favicon.ico”, host: “www.my-domain.com”, referrer: “Give yourself a better website » MY DOMAIN”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:37 +0000] “GET /favicon.ico HTTP/1.1” 502 157 “Give yourself a better website » MY DOMAIN” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| 2024/02/08 16:18:44 [error] 38#38: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET / HTTP/1.1”, upstream: “http://172.20.0.3:5000/”, host: “www.my-domain.com”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:44 +0000] “GET / HTTP/1.1” 502 157 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| 2024/02/08 16:18:44 [error] 39#39: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.137, server: www.my-domain.com, request: “GET /favicon.ico HTTP/1.1”, upstream: “http://172.20.0.3:5000/favicon.ico”, host: “www.my-domain.com”, referrer: “http://www.my-domain.com/”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:18:44 +0000] “GET /favicon.ico HTTP/1.1” 502 157 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| 2024/02/08 16:18:54 [notice] 22#22: signal 1 (SIGHUP) received from 53, reconfiguring
| 2024/02/08 16:18:54 [notice] 22#22: reconfiguring
| 2024/02/08 16:18:54 [notice] 22#22: using the “epoll” event method
| 2024/02/08 16:18:54 [notice] 22#22: start worker processes
| 2024/02/08 16:18:54 [notice] 22#22: start worker process 54
| 2024/02/08 16:18:54 [notice] 22#22: start worker process 55
| 2024/02/08 16:18:54 [notice] 22#22: start worker process 56
| 2024/02/08 16:18:54 [notice] 22#22: start worker process 57
| 2024/02/08 16:18:54 [notice] 39#39: gracefully shutting down
| 2024/02/08 16:18:54 [notice] 40#40: gracefully shutting down
| 2024/02/08 16:18:54 [notice] 38#38: gracefully shutting down
| 2024/02/08 16:18:54 [notice] 39#39: exiting
| 2024/02/08 16:18:54 [notice] 40#40: exiting
| 2024/02/08 16:18:54 [notice] 39#39: exit
| 2024/02/08 16:18:54 [notice] 40#40: exit
| 2024/02/08 16:18:54 [notice] 41#41: gracefully shutting down
| 2024/02/08 16:18:54 [notice] 41#41: exiting
| 2024/02/08 16:18:54 [notice] 41#41: exit
| 2024/02/08 16:18:54 [notice] 22#22: signal 17 (SIGCHLD) received from 40
| 2024/02/08 16:18:54 [notice] 22#22: worker process 40 exited with code 0
| 2024/02/08 16:18:54 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:18:54 [notice] 22#22: signal 17 (SIGCHLD) received from 41
| 2024/02/08 16:18:54 [notice] 22#22: worker process 41 exited with code 0
| 2024/02/08 16:18:54 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:18:54 [notice] 22#22: signal 17 (SIGCHLD) received from 39
| 2024/02/08 16:18:54 [notice] 22#22: worker process 39 exited with code 0
| 2024/02/08 16:18:54 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:18:55 [notice] 22#22: signal 1 (SIGHUP) received from 70, reconfiguring
| 2024/02/08 16:18:55 [notice] 22#22: reconfiguring
| 2024/02/08 16:18:55 [notice] 22#22: using the “epoll” event method
| 2024/02/08 16:18:55 [notice] 22#22: start worker processes
| 2024/02/08 16:18:55 [notice] 22#22: start worker process 71
| 2024/02/08 16:18:55 [notice] 22#22: start worker process 72
| 2024/02/08 16:18:55 [notice] 22#22: start worker process 73
| 2024/02/08 16:18:55 [notice] 22#22: start worker process 74
| 2024/02/08 16:18:55 [notice] 54#54: gracefully shutting down
| 2024/02/08 16:18:55 [notice] 57#57: gracefully shutting down
| 2024/02/08 16:18:55 [notice] 54#54: exiting
| 2024/02/08 16:18:55 [notice] 57#57: exiting
| 2024/02/08 16:18:55 [notice] 55#55: gracefully shutting down
| 2024/02/08 16:18:55 [notice] 55#55: exiting
| 2024/02/08 16:18:55 [notice] 56#56: gracefully shutting down
| 2024/02/08 16:18:55 [notice] 56#56: exiting
| 2024/02/08 16:18:55 [notice] 55#55: exit
| 2024/02/08 16:18:55 [notice] 56#56: exit
| 2024/02/08 16:18:55 [notice] 57#57: exit
| 2024/02/08 16:18:55 [notice] 54#54: exit
| 2024/02/08 16:18:55 [notice] 22#22: signal 17 (SIGCHLD) received from 54
| 2024/02/08 16:18:55 [notice] 22#22: worker process 54 exited with code 0
| 2024/02/08 16:18:55 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:18:55 [notice] 22#22: signal 17 (SIGCHLD) received from 57
| 2024/02/08 16:18:55 [notice] 22#22: worker process 57 exited with code 0
| 2024/02/08 16:18:55 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:18:55 [notice] 22#22: signal 17 (SIGCHLD) received from 55
| 2024/02/08 16:18:55 [notice] 22#22: worker process 55 exited with code 0
| 2024/02/08 16:18:55 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:18:55 [notice] 22#22: signal 17 (SIGCHLD) received from 56
| 2024/02/08 16:18:55 [notice] 22#22: worker process 56 exited with code 0
| 2024/02/08 16:18:55 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:19:01 [notice] 22#22: signal 1 (SIGHUP) received from 87, reconfiguring
| 2024/02/08 16:19:01 [notice] 22#22: reconfiguring
| 2024/02/08 16:19:01 [notice] 22#22: using the “epoll” event method
| 2024/02/08 16:19:01 [notice] 22#22: start worker processes
| 2024/02/08 16:19:01 [notice] 22#22: start worker process 88
| 2024/02/08 16:19:01 [notice] 22#22: start worker process 89
| 2024/02/08 16:19:01 [notice] 22#22: start worker process 90
| 2024/02/08 16:19:01 [notice] 22#22: start worker process 91
| 2024/02/08 16:19:01 [notice] 71#71: gracefully shutting down
| 2024/02/08 16:19:01 [notice] 73#73: gracefully shutting down
| 2024/02/08 16:19:01 [notice] 73#73: exiting
| 2024/02/08 16:19:01 [notice] 71#71: exiting
| 2024/02/08 16:19:01 [notice] 71#71: exit
| 2024/02/08 16:19:01 [notice] 73#73: exit
| 2024/02/08 16:19:01 [notice] 74#74: gracefully shutting down
| 2024/02/08 16:19:01 [notice] 72#72: gracefully shutting down
| 2024/02/08 16:19:01 [notice] 74#74: exiting
| 2024/02/08 16:19:01 [notice] 72#72: exiting
| 2024/02/08 16:19:01 [notice] 74#74: exit
| 2024/02/08 16:19:01 [notice] 72#72: exit
| 2024/02/08 16:19:01 [notice] 22#22: signal 17 (SIGCHLD) received from 74
| 2024/02/08 16:19:01 [notice] 22#22: worker process 74 exited with code 0
| 2024/02/08 16:19:01 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:19:01 [notice] 22#22: signal 17 (SIGCHLD) received from 73
| 2024/02/08 16:19:01 [notice] 22#22: worker process 73 exited with code 0
| 2024/02/08 16:19:01 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:19:01 [notice] 22#22: signal 17 (SIGCHLD) received from 72
| 2024/02/08 16:19:01 [notice] 22#22: worker process 71 exited with code 0
| 2024/02/08 16:19:01 [notice] 22#22: worker process 72 exited with code 0
| 2024/02/08 16:19:01 [notice] 22#22: signal 29 (SIGIO) received
| 2024/02/08 16:19:06 [notice] 38#38: exiting
| 2024/02/08 16:19:06 [notice] 38#38: exit
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:06 +0000] “GET / HTTP/1.1” 200 635 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| 2024/02/08 16:19:06 [notice] 22#22: signal 17 (SIGCHLD) received from 38
| 2024/02/08 16:19:06 [notice] 22#22: worker process 38 exited with code 0
| 2024/02/08 16:19:06 [notice] 22#22: signal 29 (SIGIO) received
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:07 +0000] “GET /57cc647b.js HTTP/1.1” 200 424024 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:07 +0000] “GET /config.js HTTP/1.1” 200 27 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:07 +0000] “GET /tippy.css HTTP/1.1” 200 661 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:07 +0000] “GET /fonts/fonts.css HTTP/1.1” 200 508 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:07 +0000] “GET /57cc647b.js HTTP/1.1” 200 424024 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:08 +0000] “GET /api/metadata/ HTTP/1.1” 401 111 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:08 +0000] “GET /fonts/Inter-roman.var.woff2?v=3.19 HTTP/1.1” 200 227180 “Give yourself a better website » MY DOMAIN” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:08 +0000] “POST /api/token/create_owner/ HTTP/1.1” 201 392 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:08 +0000] “GET /images/icon192.png HTTP/1.1” 200 5671 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:08 +0000] “GET /images/favicon.ico HTTP/1.1” 200 4286 “http://www.my-domain.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “172.20.0.3:5000”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:24 +0000] “GET /firstrun HTTP/2.0” 500 177 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “-”
| www.my-domain.com 192.168.0.137 - - [08/Feb/2024:16:19:24 +0000] “GET /favicon.ico HTTP/2.0” 500 177 “Give yourself a better website » MY DOMAIN” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0” “-”

joea · February 8, 2024, 10:10pm

@DavidMStraub @emyoulation I’ve wondered for a bit now, if this is a normal error if only the default certificate was installed. There seemed no hint of this in the documentation. Sadly, it slipped my mind earlier. I feel quite foolish now.

While sniffing about, I ran across this in the nginx default.conf and it seems a 500 error is “normal and expected” in such case?

joea@gramps-web-d:~$ docker exec -it nginx-proxy bash
root@b8b1781a53fb:/app# cat /etc/nginx/conf.d/default.conf

nginx-proxy version : 1.4.0-75-g3d61f47

. . .
server {
server_name my-domain.com;
access_log /var/log/nginx/access.log vhost;
http2 on;
listen 80 ;
listen 443 ssl ;
# No certificate found for this vhost, so use the default certificate and
# return an error code if the user connects via https.
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
if ($https) {
return 500;
}
include /etc/nginx/vhost.d/default;
location / {
proxy_pass http://my-domain.com;
set $upstream_keepalive false;
}
}
. . .

The latter parts of this post appear to be superfluous and perhaps should be deleted?

I tagged you both to attempt to get this read before all the previous stuff. Ah, learning is hard some days.

DavidMStraub · February 9, 2024, 6:55am

This is a problem:

grampsweb_celery | INFO:gramps_webapi:Rebuilding search index …
grampsweb_celery | Traceback (most recent call last):
grampsweb_celery | File “”, line 198, in _run_module_as_main
grampsweb_celery | File “”, line 88, in _run_code
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/main.py”, line 202, in
grampsweb_celery | cli(
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1157, in call
grampsweb_celery | return self.main(*args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1078, in main
grampsweb_celery | rv = self.invoke(ctx)
grampsweb_celery | ^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1688, in invoke
grampsweb_celery | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1688, in invoke
grampsweb_celery | return _process_result(sub_ctx.command.invoke(sub_ctx))
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 1434, in invoke
grampsweb_celery | return ctx.invoke(self.callback, **ctx.params)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/core.py”, line 783, in invoke
grampsweb_celery | return __callback(*args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/click/decorators.py”, line 33, in new_func
grampsweb_celery | return f(get_current_context(), *args, **kwargs)
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/main.py”, line 149, in index_full
grampsweb_celery | db = db_manager.get_db().db
grampsweb_celery | ^^^^^^^^^^^^^^^^^^^
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/dbmanager.py”, line 177, in get_db
grampsweb_celery | smgr.open_activate(
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/dbloader.py”, line 119, in open_activate
grampsweb_celery | self.read_file(filename, mode, username, password)
grampsweb_celery | File “/usr/local/lib/python3.11/dist-packages/gramps_webapi/dbloader.py”, line 98, in read_file
grampsweb_celery | self.dbstate.db.load(
grampsweb_celery | File “/usr/lib/python3/dist-packages/gramps/gen/db/generic.py”, line 597, in load
grampsweb_celery | self._create_schema()
grampsweb_celery | File “/usr/lib/python3/dist-packages/gramps/plugins/db/dbapi/dbapi.py”, line 75, in _create_schema
grampsweb_celery | self.dbapi.execute('CREATE TABLE person ’
grampsweb_celery | File “/usr/lib/python3/dist-packages/gramps/plugins/db/dbapi/sqlite.py”, line 133, in execute
grampsweb_celery | self.__cursor.execute(*args, **kwargs)
grampsweb_celery | sqlite3.OperationalError: table person already exists

I have to look into what is causing it.

This is also a problem:

nginx-proxy-acme | [Thu Feb 8 16:19:18 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/ei2wfvsu_woz5hTyVBhAlbRz7H35Ba7_soKmgxjtuR8:

It means you haven’t set up your domain or the acme companion correctly. Might have something to do with you using two host names separated by comma - no clue if that’s allowed, you’ll have to look into that project’s documentation. This is completely independent of Gramps Web.

joea · February 9, 2024, 2:27pm

DavidMStraub:

. . .I have to look into what is causing it.

This is also a problem:
nginx-proxy-acme | [Thu Feb 8 16:19:18 UTC 2024] Invalid status, www.my-domain.com:Verify error detail:24.103.49.18: Invalid response from http://www.my-domain.com/.well-known/acme-challenge/ei2wfvsu_woz5hTyVBhAlbRz7H35Ba7_soKmgxjtuR8:
It means you haven’t set up your domain or the acme companion correctly. Might have something to do with you using two host names separated by comma - no clue if that’s allowed, you’ll have to look into that project’s documentation. This is completely independent of Gramps Web.

Before you get too deep, perhaps I should mention there is IP forwarding going on at the router, the single available static IP is fowarded to an apache host that serves an application on it’s hardware and forwards the domains in question to the VM that hosts grampsweb.

Perhaps “attempts to forward, properly” would be more accurate?

I’ll look into how to correctly manage that part as well.

joea · February 9, 2024, 5:11pm

After adjusting the apache host reverse-proxy/proxy-ssl setting, gramps web can be accessed from off site.

There is a warning about the certificate, which is due to “wrong domain”. That I do not understand as the cert, via docker exec nginx-proxy-acme /app/cert_status shows the domains are correct.

That’s not a grampsweb issue as such.

Thanks for the help.

joea · February 9, 2024, 11:26pm

FYI sort of thing, it appears the issue is apache cannot, or I don’t know how to, “pass through” the actual certificates.

So, have to, at least for now, manually copy them from the docker container to the apache “front end” and configure a virtual host certificate in the traditional manner. And, of course, cobble up a way to do that every time the certs update.

Never too old to learn. Someone told me that’s good thing.

Topic		Replies	Views
Error 502 => self hosting Gramps Web	1	47	October 21, 2024
502 Bad Gateway when using provided docker-compose.yml Gramps Web	5	1647	July 15, 2023
Hosting Gramps Web on existing personal web server? Gramps Web	2	182	July 27, 2024
Gramps web docker novice Gramps Web	5	224	October 10, 2024
Setup Issues: Gramps Web on VPS with SSL Gramps Web	35	1479	April 7, 2024

503 error nginx

nginx-proxy version : 1.4.0-75-g3d61f47

Related topics