Bad gateway po aktualizacji do v22.12

Moderator: fracz

marik_te
Posts: 31
Joined: Thu May 13, 2021 2:50 pm

Post

Witam. Mam problem z dostaniem sie do supli po aktualizacji do v22.12. Wszystko startuje prawidlowo, lecz przez www mam komunikat bad gateway. Supla pracuje w trybie proxy. W tym samym czasie skrypty rowniez w trybie proxy dzialaja. Po przelaczeniu supli w tryb standalone dziala prawidlowo. Probowalem instalowac na nowo lecz bez skutecznie.
Jak mozna zrobic downhrade? Moze to pomoze.
User avatar
pzygmunt
Posts: 18604
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków

Post

Sprawdź logi
marik_te
Posts: 31
Joined: Thu May 13, 2021 2:50 pm

Post

Uruchomione kontenery:

Code: Select all

CONTAINER ID   IMAGE                           COMMAND                  CREATED              STATUS                        PORTS                                                           NAMES
8fd2301e5b22   supla/supla-server              "/usr/bin/server-ent…"   About a minute ago   Up About a minute (healthy)   0.0.0.0:2015-2016->2015-2016/tcp, :::2015-2016->2015-2016/tcp   supla-server
73edeaa66c1d   supla/supla-cloud               "docker-php-entrypoi…"   About a minute ago   Up About a minute (healthy)   80/tcp                                                          supla-cloud
ec1c59238199   mysql:5.7.20                    "docker-entrypoint.s…"   About a minute ago   Up About a minute             3306/tcp                                                        supla-db
2bcdcefebf24   nginx:stable-alpine             "/docker-entrypoint.…"   36 hours ago         Up 11 hours                   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp                        proxy-web-auto
6a3232df9da6   nginxproxy/acme-companion:2.1   "/bin/bash /app/entr…"   36 hours ago         Up 11 hours                                                                                   letsencrypt-auto
7f7acc6a9d99   nginxproxy/docker-gen:0.7.7     "/usr/local/bin/dock…"   36 hours ago         Up 11 hours                                                                                   docker-gen-auto
199e3835823b   suplascripts_suplascripts       "docker-php-entrypoi…"   38 hours ago         Up 11 hours                   80/tcp                                                          suplascripts
8e1aa1e8b653   mysql:5.7                       "docker-entrypoint.s…"   38 hours ago         Up 11 hours                   3306/tcp, 33060/tcp                                             suplascripts-db
Logi z clouda:

Code: Select all

Database connection has been established.

                    Application Migrations


No migrations to execute.

 [OK] The "async" transport was set up successfully.

Client for webapp exists.

 // Warming up the cache for the prod environment with debug
 // false

 [OK] Cache for the "prod" environment (debug=false) was successfully warmed.

User admin@lakie.waw.pl already exists.
2023-01-06 08:22:29,810 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-01-06 08:22:29,835 INFO supervisord started with pid 1
2023-01-06 08:22:30,838 INFO spawned: 'apache' with pid 38
2023-01-06 08:22:30,842 INFO spawned: 'cron' with pid 39
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.21.0.2. Set the 'ServerName' directive globally to suppress this message
[Fri Jan 06 08:22:31.009594 2023] [ssl:warn] [pid 38] AH01906: 172.21.0.2:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Fri Jan 06 08:22:31.011243 2023] [ssl:warn] [pid 38] AH01909: 172.21.0.2:443:0 server certificate does NOT include an ID which matches the server name
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.21.0.2. Set the 'ServerName' directive globally to suppress this message
[Fri Jan 06 08:22:31.054515 2023] [ssl:warn] [pid 38] AH01906: 172.21.0.2:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Fri Jan 06 08:22:31.055181 2023] [ssl:warn] [pid 38] AH01909: 172.21.0.2:443:0 server certificate does NOT include an ID which matches the server name
[Fri Jan 06 08:22:31.059949 2023] [mpm_prefork:notice] [pid 38] AH00163: Apache/2.4.52 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Fri Jan 06 08:22:31.060421 2023] [core:notice] [pid 38] AH00094: Command line: 'apache2 -D FOREGROUND'
2023-01-06 08:22:32,074 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-06 08:22:32,075 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
172.21.0.2:80 127.0.0.1 - - [06/Jan/2023:08:22:46 +0000] "HEAD /api/server-info HTTP/1.1" 200 289 "-" "Wget/1.21"
172.21.0.2:80 172.19.0.4 - - [06/Jan/2023:08:22:50 +0000] "HEAD /api/server-status HTTP/1.1" 200 289 "-" "Wget/1.18 (linux-gnu)"

supla:clean:passed-io-client-registration-dates
-----------------------------------------------

Client registration expiration date - cleared: 0
I/O Device registration expiration date - cleared: 0

supla:clean:disable-demo-client-apps
------------------------------------

Clients to disable: 0

supla:cyclic:send-server-messages
---------------------------------


172.21.0.2:80 127.0.0.1 - - [06/Jan/2023:08:23:16 +0000] "HEAD /api/server-info HTTP/1.1" 200 289 "-" "Wget/1.21"
Logi z servera:

Code: Select all

2023-01-06 08:21:56,535 CRIT Supervisor running as root (no user in config file)
2023-01-06 08:21:56,590 INFO supervisord started with pid 1
2023-01-06 08:21:57,592 INFO spawned: 'supla-scheduler' with pid 22
2023-01-06 08:21:57,698 INFO spawned: 'supla-server' with pid 23
INFO[08:21:57.792500] Server version 22.12.01 [Protocol v19]
INFO[08:21:57.794569] Started at Fri Jan  6 08:21:57 2023
INFO[08:21:57.834538] Scheduler version 22.07.01
INFO[08:21:57.835091] Started at Fri Jan  6 08:21:57 2023
INFO[08:21:58.120596] SSL version: LibreSSL 3.5.3
ERR[08:21:58.156489] SSL certificate expired!
INFO[08:21:58.269318] Connection accepted: 192.168.100.23:57368 ClientSD: 13 Secure: 0
INFO[08:21:58.319397] Connection accepted: 46.238.237.250:55067 ClientSD: 17 Secure: 0
INFO[08:21:58.457012] Connection accepted: 192.168.100.24:59003 ClientSD: 20 Secure: 0
INFO[08:21:58.459509] Device registration started. ClientSD: 13 Protocol Version: 12 ThreadID: 31 GUID: 625414D7
INFO[08:21:58.460559] Device registration started. ClientSD: 20 Protocol Version: 16 ThreadID: 33 GUID: 71686E1C
INFO[08:21:58.550379] Device registration started. ClientSD: 17 Protocol Version: 12 ThreadID: 32 GUID: D7CFC353
INFO[08:21:58.717504] Connection accepted: 46.238.237.69:54748 ClientSD: 23 Secure: 0
2023-01-06 08:21:58,718 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-06 08:21:58,718 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[08:21:58.915653] Device registration started. ClientSD: 23 Protocol Version: 12 ThreadID: 34 GUID: 7E61803B
INFO[08:21:59.086414] Device registered. ID: 3, ClientSD: 17 Protocol Version: 12 ThreadID: 32 GUID: D7CFC353 ResultCode: 3
INFO[08:21:59.107260] Device registered. ID: 5, ClientSD: 13 Protocol Version: 12 ThreadID: 31 GUID: 625414D7 ResultCode: 3
INFO[08:21:59.185783] Device registered. ID: 39, ClientSD: 20 Protocol Version: 16 ThreadID: 33 GUID: 71686E1C ResultCode: 3
INFO[08:21:59.316299] Device registered. ID: 13, ClientSD: 23 Protocol Version: 12 ThreadID: 34 GUID: 7E61803B ResultCode: 3
INFO[08:21:59.756474] Connection accepted: 192.168.100.17:41562 ClientSD: 14 Secure: 1
INFO[08:21:59.791553] Connection accepted: 192.168.100.16:63775 ClientSD: 29 Secure: 0
INFO[08:21:59.793584] Connection accepted: 192.168.100.15:57001 ClientSD: 45 Secure: 0
INFO[08:21:59.800491] Device registration started. ClientSD: 45 Protocol Version: 12 ThreadID: 51 GUID: 13BF6F94
INFO[08:21:59.884250] Connection accepted: 192.168.100.19:51730 ClientSD: 48 Secure: 0
INFO[08:21:59.888785] Device registration started. ClientSD: 29 Protocol Version: 12 ThreadID: 50 GUID: 0F15DA5A
INFO[08:21:59.931613] Device registered. ID: 20, ClientSD: 45 Protocol Version: 12 ThreadID: 51 GUID: 13BF6F94 ResultCode: 3
INFO[08:22:00.088418] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 14
INFO[08:22:00.132290] Connection accepted: 192.168.100.18:41560 ClientSD: 39 Secure: 1
INFO[08:22:00.144688] Device registration started. ClientSD: 48 Protocol Version: 12 ThreadID: 53 GUID: ADF1C164
INFO[08:22:00.149156] Connection accepted: 192.168.100.22:52597 ClientSD: 53 Secure: 0
INFO[08:22:00.170446] Connection accepted: 192.168.100.14:49901 ClientSD: 56 Secure: 0
INFOINFO[08:22:00.193691] Device registration started. ClientSD: 14 Protocol Version: 12 ThreadID: 49 GUID: EEA0FFCD
[08:22:00.242941] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 39
INFO[08:22:00.305281] Device registration started. ClientSD: 56 Protocol Version: 12 ThreadID: 56 GUID: A7102572
INFO[08:22:00.370356] Device registration started. ClientSD: 39 Protocol Version: 12 ThreadID: 54 GUID: BBD48DE6
INFO[08:22:00.469636] Device registration started. ClientSD: 53 Protocol Version: 16 ThreadID: 55 GUID: 9095C393
INFO[08:22:00.540213] Device registered. ID: 9, ClientSD: 48 Protocol Version: 12 ThreadID: 53 GUID: ADF1C164 ResultCode: 3
INFO[08:22:00.839415] Device registered. ID: 26, ClientSD: 29 Protocol Version: 12 ThreadID: 50 GUID: 0F15DA5A ResultCode: 3
INFO[08:22:00.949139] Device registered. ID: 28, ClientSD: 14 Protocol Version: 12 ThreadID: 49 GUID: EEA0FFCD ResultCode: 3
INFO[08:22:01.053022] Device registered. ID: 22, ClientSD: 56 Protocol Version: 12 ThreadID: 56 GUID: A7102572 ResultCode: 3
INFO[08:22:01.167391] Device registered. ID: 19, ClientSD: 39 Protocol Version: 12 ThreadID: 54 GUID: BBD48DE6 ResultCode: 3
INFO[08:22:01.652779] Device registered. ID: 30, ClientSD: 53 Protocol Version: 16 ThreadID: 55 GUID: 9095C393 ResultCode: 3
ERR[08:22:02.773170] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:02.875510] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:04.447858] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
INFO[08:22:04.573165] Connection accepted: 192.168.100.1:55084 ClientSD: 59 Secure: 0
ERR[08:22:04.700731] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:04.711978] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
INFO[08:22:04.740944] Device registration started. ClientSD: 59 Protocol Version: 16 ThreadID: 110 GUID: 3C10E158
INFO[08:22:04.823429] Device registered. ID: 47, ClientSD: 59 Protocol Version: 16 ThreadID: 110 GUID: 3C10E158 ResultCode: 3
ERR[08:22:05.166314] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:06.842999] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:06.858740] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:06.872629] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:06.875221] GoogleHomeGraph client error userId: 2, code=404, message={"message":"HomeGraph error message: Requested entity was not found."}
ERR[08:22:12.692332] GoogleHomeGraph client error userId: 2, code=404, message={"message":"Sync request error. HomeGraph error message: Requested entity was not found."}
INFO[08:22:19.099150] Connection accepted: 46.238.237.250:16190 ClientSD: 36 Secure: 1
INFO[08:22:19.205441] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 36
INFO[08:22:19.327891] Device registration started. ClientSD: 36 Protocol Version: 10 ThreadID: 163 GUID: DFF4087D
INFO[08:22:19.474760] Device registered. ID: 4, ClientSD: 36 Protocol Version: 10 ThreadID: 163 GUID: DFF4087D ResultCode: 3
INFO[08:22:20.623253] Connection accepted: 192.168.100.20:21945 ClientSD: 30 Secure: 1
INFO[08:22:20.757262] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 30
INFO[08:22:20.876590] Device registration started. ClientSD: 30 Protocol Version: 10 ThreadID: 165 GUID: 4CBC7E75
INFO[08:22:20.904967] Device registered. ID: 2, ClientSD: 30 Protocol Version: 10 ThreadID: 165 GUID: 4CBC7E75 ResultCode: 3
INFO[08:22:46.857776] Connection accepted: 192.168.100.1:39524 ClientSD: 33 Secure: 1
INFO[08:22:46.960659] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 33
INFO[08:22:47.124309] Device registration started. ClientSD: 33 Protocol Version: 10 ThreadID: 180 GUID: 5E4C3D28
INFO[08:22:47.144568] Device registered. ID: 1, ClientSD: 33 Protocol Version: 10 ThreadID: 180 GUID: 5E4C3D28 ResultCode: 3
INFO[08:22:51.421604] Connection accepted: 192.168.100.1:43752 ClientSD: 41 Secure: 1
INFO[08:22:51.429073] Cipher: ECDHE-RSA-AES128-GCM-SHA256, SSL Version: TLSv1.2, ClientSD: 41
INFO[08:22:51.435103] Connection accepted: 192.168.100.1:49330 ClientSD: 65 Secure: 0
INFO[08:23:51.653598] Connection accepted: 192.168.100.1:36340 ClientSD: 60 Secure: 1
INFO[08:23:51.660081] Cipher: ECDHE-RSA-AES128-GCM-SHA256, SSL Version: TLSv1.2, ClientSD: 60
INFO[08:23:51.666783] Connection accepted: 192.168.100.1:44572 ClientSD: 62 Secure: 0
Logi z bazy danych:

Code: Select all

2023-01-06T08:21:43.898945Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-01-06T08:21:43.915493Z 0 [Note] mysqld (mysqld 5.7.20) starting as process 1 ...
2023-01-06T08:21:43.942103Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-01-06T08:21:43.942432Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-01-06T08:21:43.942636Z 0 [Note] InnoDB: Uses event mutexes
2023-01-06T08:21:43.942771Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-01-06T08:21:43.942890Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2023-01-06T08:21:43.942993Z 0 [Note] InnoDB: Using Linux native AIO
2023-01-06T08:21:43.945858Z 0 [Note] InnoDB: Number of pools: 1
2023-01-06T08:21:43.947401Z 0 [Note] InnoDB: Using CPU crc32 instructions
2023-01-06T08:21:43.973186Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2023-01-06T08:21:44.048952Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023-01-06T08:21:44.058762Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2023-01-06T08:21:44.207938Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2023-01-06T08:21:44.625471Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-01-06T08:21:44.625643Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-01-06T08:21:45.359666Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-01-06T08:21:45.361392Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-01-06T08:21:45.361449Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2023-01-06T08:21:45.364843Z 0 [Note] InnoDB: Waiting for purge to start
2023-01-06T08:21:45.418643Z 0 [Note] InnoDB: 5.7.20 started; log sequence number 431222664
2023-01-06T08:21:45.419102Z 0 [Note] Plugin 'FEDERATED' is disabled.
2023-01-06T08:21:45.429814Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-01-06T08:21:45.501717Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2023-01-06T08:21:45.653913Z 0 [Warning] CA certificate ca.pem is self signed.
2023-01-06T08:21:45.663104Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2023-01-06T08:21:45.663561Z 0 [Note] IPv6 is available.
2023-01-06T08:21:45.663706Z 0 [Note]   - '::' resolves to '::';
2023-01-06T08:21:45.663861Z 0 [Note] Server socket created on IP: '::'.
2023-01-06T08:21:47.536705Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:47.537500Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:47.537532Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:47.539310Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:47.539350Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:47.848413Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:49.241378Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:49.241425Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2023-01-06T08:21:53.512803Z 0 [Note] Event Scheduler: Loaded 0 events
2023-01-06T08:21:53.829637Z 0 [Note] mysqld: ready for connections.
Version: '5.7.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
2023-01-06T08:21:53.829838Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2023-01-06T08:21:53.829971Z 0 [Note] Beginning of list of non-natively partitioned tables
2023-01-06T08:21:57.660824Z 0 [Note] End of list of non-natively partitioned tables
2023-01-06T08:21:59.307304Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230106  8:21:59
Logi z proxy:

Code: Select all

scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:53 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:53 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:54 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:54 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:56 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:56 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:57 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:23:58 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:00 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
supla.lakie.waw.pl 51.83.247.41 - - [06/Jan/2023:08:24:03 +0000] "POST /oauth/v2/token HTTP/2.0" 502 157 "-" "-"
2023/01/06 08:24:03 [error] 61#61: *40624 no live upstreams while connecting to upstream, client: 51.83.247.41, server: supla.lakie.waw.pl, request: "POST /oauth/v2/token HTTP/2.0", upstream: "http://supla.lakie.waw.pl/oauth/v2/token", host: "supla.lakie.waw.pl"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:10 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:10 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:10 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:13 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:16 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:16 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:17 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:17 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:18 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:20 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:24 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:24 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:29 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:29 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:29 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:29 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:30 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:30 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:30 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:33 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:36 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:37 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:43 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:56 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:56 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:57 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:24:58 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:00 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:00 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:02 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:03 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:03 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:04 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:06 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:10 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:10 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:16 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:17 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:19 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:20 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:20 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:20 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:23 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:23 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:23 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:29 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:29 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:30 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:36 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:36 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:37 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:39 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:39 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:40 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:42 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:43 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:44 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:49 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:50 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:56 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:58 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:25:59 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:00 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:03 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:08 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
2023/01/06 08:26:09 [error] 61#61: *40785 no live upstreams while connecting to upstream, client: 51.83.210.49, server: supla.lakie.waw.pl, request: "POST /oauth/v2/token HTTP/2.0", upstream: "http://supla.lakie.waw.pl/oauth/v2/token", host: "supla.lakie.waw.pl"
supla.lakie.waw.pl 51.83.210.49 - - [06/Jan/2023:08:26:09 +0000] "POST /oauth/v2/token HTTP/2.0" 502 157 "-" "-"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:09 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:10 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:13 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:13 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:16 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:16 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:16 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
scripts.lakie.waw.pl 192.168.100.1 - - [06/Jan/2023:08:26:18 +0000] "POST /api/state-webhook HTTP/1.1" 202 15 "-" "supla-server"
Spróbowałem usunąć wszystkie kontenery i zainstalowaćna nowo. Zauważyłem że pewne paczki pobierane podczas instalacji już istniały w systemie. Może to w nich jest jakiś problem. Co należy jeszcze usunąć żeby zrobić typowy clean install?
supla.png
You do not have the required permissions to view the files attached to this post.
marik_te
Posts: 31
Joined: Thu May 13, 2021 2:50 pm

Post

Poradziłem sobie z tym problemem. Szkoda tylko że mimo różnych prób jedynym logicznym rozwiązaniem było przywrócenie backupu.
Pomału zaczynam myśleć, że supla kultywuje zasadę "działa, nie dotykaj". No trudno.

Return to “supla-docker”