[tutorial] Raspberry Pi – Docker, Proxy, Let’s Encrypt, SUPLA, SUPLA-Scripts...

User avatar
lesny8
Posts: 3132
Joined: Mon Dec 11, 2017 9:43 pm
Has thanked: 10 times
Been thanked: 9 times

Post

_aro_ wrote: Thu Feb 14, 2019 8:24 pm Po przeczytaniu że należy je zmienic zmieniłem je i mam teraz: zewnetrzne 81 na wewnętrzne 80 na 192.168.0.250 oraz zewnetrzne 444 na wewnętrzne 443 na ten sam IP.
Namieszałeś z tymi portami
WAN 80 -> LAN 81
WAN 443 -> LAN 444
Tak pisali, a Ty zrobiłeś odwrotnie ;)
SOP 2023 :heavy_check_mark:
SOP 2024 :heavy_check_mark:
Czekam na kolejne Supla Offline Party :upside_down_face:
🧩: 🔑cz->b ⛴️+ila
Top
_aro_
Posts: 51
Joined: Mon Apr 09, 2018 5:10 pm
Location: Legnica

Post

Dzieki wielkie !

Rzeczywiście tu się zamieszałem troszkę :D Ustawiłem mapowanie portów na routerze poprawnie, odinstalowałem wszystko i próbuję jeszcze raz.
Pewne postęy są :D

Trzy kontenery się uruchomiły:

Code: Select all

2e7d603bc612        jwilder/docker-gen                       "/usr/local/bin/do..."   37 minutes ago      Up 37 minutes                                                                                nginx-gen
da28de8856fc        jrcs/letsencrypt-nginx-proxy-companion   "/bin/bash /app/en..."   37 minutes ago      Up 15 minutes                                                                                nginx-letsencrypt
445ef386bf88        nginx                                    "nginx -g 'daemon ..."   37 minutes ago      Up 37 minutes           0.0.0.0:81->80/tcp, 0.0.0.0:444->443/tcp                             nginx-web
docker logs --tail=50 nginx-letsencrypt pokazuje:

Code: Select all

Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container 445ef386bf8850499d9d1f151aab0f2acb1687924a84129d941)...
2019/02/15 00:47:44 Generated '/app/letsencrypt_service_data' from 10 containers
2019/02/15 00:47:44 Running '/app/signal_le_service'
2019/02/15 00:47:44 Watching docker events
2019/02/15 00:47:44 Contents of /app/letsencrypt_service_data did not change. Skipping '/app/signal_le_service'
Sleep for 3600s
This is going to take a long time
Info: Diffie-Hellman group creation complete, reloading nginx.
Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container 445ef386bf8850499d9d1f151aab0f2acb1687924a84129d941)...
2019/02/15 01:02:15 Received event start for container 6e63130c4e74
2019/02/15 01:02:22 Received event start for container bf107e948831
2019/02/15 01:02:27 Received event start for container 3ae91054d1fc
2019/02/15 01:02:42 Debounce minTimer fired
2019/02/15 01:02:42 Generated '/app/letsencrypt_service_data' from 13 containers
2019/02/15 01:02:42 Running '/app/signal_le_service'
/etc/nginx/certs/supla.arnet24.pl /app
Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container 445ef386bf8850499d9d1f151aab0f2acb1687924a84129d941)...
Creating/renewal supla.arnet24.pl certificates... (supla.arnet24.pl)
2019-02-15 01:02:48,529:INFO:simp_le:1382: Generating new account key
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1584, in main
    return main_with_exceptions(cli_args)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1567, in main_with_exceptio
    persist_new_data(args, existing_data)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1457, in persist_new_data
    client = registered_client(args, existing_data.account_key)
  File "/usr/lib/python2.7/site-packages/simp_le.py", line 1395, in registered_client
    client = acme_client.Client(directory=args.server, key=key, net=net)
  File "/usr/lib/python2.7/site-packages/acme/client.py", line 257, in __init__
    net.get(directory).json())
  File "/usr/lib/python2.7/site-packages/acme/client.py", line 1152, in get
    self._send_request('GET', url, **kwargs), content_type=content_type)
  File "/usr/lib/python2.7/site-packages/acme/client.py", line 1101, in _send_request
    response = self.session.request(method, url, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
ConnectionError: HTTPSConnectionPool(host='acme-v01.api.letsencrypt.org', port=443): Mceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.Verifieion object at 0x7f0aea34cb90>: Failed to establish a new connection: [Errno -3] Try ag

Unhandled error has happened, traceback is above

Debugging tips: -v improves output verbosity. Help is available under --help.
/app
Sleep for 3600s
Problem z połączeniem ? Spróbować jutro ?

Potem coś z kontenerem supla-db - takie logi:

Code: Select all

2019-02-15T01:34:27.432507Z 0 [Note] Beginning of list of non-natively partitioned tables
2019-02-15T01:34:27.468415Z 0 [Note] End of list of non-natively partitioned tables
2019-02-15T01:34:33.490483Z 3 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:34:33.524532Z 4 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:34:42.284155Z 5 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:34:48.294513Z 6 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:34:55.300613Z 7 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:35:03.307559Z 8 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:35:12.313857Z 9 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:35:22.320472Z 10 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:35:33.326507Z 11 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:35:45.332632Z 12 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:35:58.339449Z 13 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:36:12.345525Z 14 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:36:27.351721Z 15 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T01:36:27.385024Z 16 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
Ten z kolei co ma się podłączyć chyba do bazy danych: docker logs --tail=100 supla-cloud:

Code: Select all

In PDOConnection.php line 43:

  SQLSTATE[HY000] [1045] Access denied for user 'supla'@'172.22.0.3' (using p
  assword: YES)


doctrine:migrations:migrate [--write-sql] [--dry-run] [--query-time] [--allow-no-migration] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]

Waiting for database connection (10)...
Waiting for database connection (9)...
Waiting for database connection (8)...
Waiting for database connection (7)...
Waiting for database connection (6)...
Waiting for database connection (5)...
Waiting for database connection (4)...
Waiting for database connection (3)...
Waiting for database connection (2)...
Waiting for database connection (1)...

In AbstractMySQLDriver.php line 103:

  An exception occured in driver: SQLSTATE[HY000] [1045] Access denied for us
  er 'supla'@'172.22.0.3' (using password: YES)
Ten pisze, że używa hasła - bo jest przecież w pliku .env DB_PASSWORD=... i SECRET=...
Ten drugi się nie podłącza - ot zagwozdka ...
Top
edm
Posts: 677
Joined: Mon Jan 15, 2018 6:18 pm
Been thanked: 2 times

Post

lesny8 wrote: Mon Dec 03, 2018 1:19 am ...(nowa karta tym razem Industrial, bo stara padła)
Proszę o linka do tej karty Industrial.
Wziąłem udział w Supla Offline Party 2023 :D
Top
_aro_
Posts: 51
Joined: Mon Apr 09, 2018 5:10 pm
Location: Legnica

Post

i jeszcze docker logs --tail=50 supla-server:

Code: Select all

INFO[1550224665.602346] Started at Fri Feb 15 09:57:45 2019
ERR[1550224665.606641] MySQL - Failed to connect to database.
ERR[1550224665.606667] Can't connect to database!
2019-02-15 09:57:45,608 INFO exited: supla-scheduler (exit status 1; not expected)
INFO[1550224665.610685] Server version 2.3.0 [Protocol v10]
2019-02-15 09:57:45,611 INFO gave up: supla-scheduler entered FATAL state, too many start retries too quickly
INFO[1550224665.610819] Started at Fri Feb 15 09:57:45 2019
ERR[1550224665.614654] MySQL - Failed to connect to database.
ERR[1550224665.614675] Can't connect to database!
2019-02-15 09:57:45,615 INFO exited: supla-server (exit status 1; not expected)
2019-02-15 09:57:46,617 INFO gave up: supla-server entered FATAL state, too many start retries too quickly
2019-02-15 09:58:37,675 WARN received SIGTERM indicating exit request
2019-02-15 09:59:58,446 CRIT Supervisor running as root (no user in config file)
2019-02-15 09:59:58,451 INFO supervisord started with pid 1
2019-02-15 09:59:59,455 INFO spawned: 'supla-scheduler' with pid 10
2019-02-15 09:59:59,458 INFO spawned: 'supla-server' with pid 11
INFO[1550224799.468835] Scheduler version 2.3.0
Top
_aro_
Posts: 51
Joined: Mon Apr 09, 2018 5:10 pm
Location: Legnica

Post

Problem pomiędzy supla-server, supla-cloud i supla-db. Kontener supla-cloud się restartuje, logi tak wyglądają:

Code: Select all

docker logs --tail=50 supla-cloud
In PDOConnection.php line 43:

  SQLSTATE[HY000] [1045] Access denied for user 'supla'@'172.22.0.3' (using p
  assword: YES)


doctrine:migrations:migrate [--write-sql] [--dry-run] [--query-time] [--allow-no-migration] [--configuration [CONFIGURATION]] [--db-configuration [DB-CONFIGURATION]] [--db DB] [--em EM] [--shard SHARD] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<version>]

Waiting for database connection (10)...
Waiting for database connection (9)...
Waiting for database connection (8)...

Code: Select all

docker logs --tail=50 supla-server
2019-02-15 11:01:32,449 INFO spawned: 'supla-scheduler' with pid 10
2019-02-15 11:01:32,453 INFO spawned: 'supla-server' with pid 11
INFO[1550228492.839054] Scheduler version 2.3.0
INFO[1550228492.839848] Started at Fri Feb 15 11:01:32 2019
INFO[1550228492.840085] Server version 2.3.0 [Protocol v10]
INFO[1550228492.840195] Started at Fri Feb 15 11:01:32 2019
ERR[1550228492.917768] MySQL - Failed to connect to database.
ERR[1550228492.918107] MySQL - Failed to connect to database.
ERR[1550228492.918123] Can't connect to database!
2019-02-15 11:01:32,919 INFO exited: supla-scheduler (exit status 1; not expected)
ERR[1550228492.919108] Can't connect to database!

Code: Select all

docker logs --tail=50 supla-db
2019-02-15T11:22:22.178138Z 147 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T11:22:22.212723Z 148 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T11:22:31.521834Z 149 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T11:22:37.532215Z 150 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T11:22:44.538305Z 151 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
2019-02-15T11:22:52.544316Z 152 [Note] Access denied for user 'supla'@'172.22.0.3' (using password: YES)
Widzę, że w pliku /supla-docker/docker-compose.yml jest miejsce dla tych haseł:

Code: Select all

supla-db:
    container_name: ${COMPOSE_PROJECT_NAME}-db
    restart: unless-stopped
    image: mysql:5.7.20
    env_file:
      - .env.default
      - .env
    environment:
      MYSQL_ROOT_PASSWORD: ${DB_PASSWORD}
      MYSQL_DATABASE: supla
      MYSQL_USER: supla
      MYSQL_PASSWORD: ${DB_PASSWORD}
    volumes:
      - ${VOLUME_DATA}/mysql:/var/lib/mysql:z
tylko, że jako zmienne deklarowane gdzie indziej. Wpisałem tutaj na sztywno hasło DB_PASSWORD z pliku /supla-docker/.env bez tego SECRET bo nie wiem co z tym zrobić:

Code: Select all

DB_PASSWORD=UcFrkB1kj3H0Eu4XPgQPO2zX89ZY3ybG
SECRET=1zjkWCEWI8W1kzQjaYS2xN6fNOut1DQb
ale dalej nic - tzn. po próbie podłączenia się do bazy danych

Code: Select all

docker exec -it supla-db mysql -u root -p
mam

Code: Select all

Enter password:
wpisuję to DB_PASSWORD i mam:

Code: Select all

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Jakieś wskazówki ?
Top
User avatar
lesny8
Posts: 3132
Joined: Mon Dec 11, 2017 9:43 pm
Has thanked: 10 times
Been thanked: 9 times

Post

Sprawdź użytkownik 'supla' a nie 'root'
SOP 2023 :heavy_check_mark:
SOP 2024 :heavy_check_mark:
Czekam na kolejne Supla Offline Party :upside_down_face:
🧩: 🔑cz->b ⛴️+ila
Top
User avatar
lesny8
Posts: 3132
Joined: Mon Dec 11, 2017 9:43 pm
Has thanked: 10 times
Been thanked: 9 times

Post

edm wrote: Fri Feb 15, 2019 5:30 am
lesny8 wrote: Mon Dec 03, 2018 1:19 am ...(nowa karta tym razem Industrial, bo stara padła)
Proszę o linka do tej karty Industrial.
https://allegro.pl/kategoria/karty-pami ... e-1-0-0131
SOP 2023 :heavy_check_mark:
SOP 2024 :heavy_check_mark:
Czekam na kolejne Supla Offline Party :upside_down_face:
🧩: 🔑cz->b ⛴️+ila
Top
_aro_
Posts: 51
Joined: Mon Apr 09, 2018 5:10 pm
Location: Legnica

Post

nope :(

Code: Select all

docker exec -it supla-db mysql -u supla -p
Enter password:
ERROR 1045 (28000): Access denied for user 'supla'@'localhost' (using password: YES)
Top
User avatar
lesny8
Posts: 3132
Joined: Mon Dec 11, 2017 9:43 pm
Has thanked: 10 times
Been thanked: 9 times

Post

Code: Select all

source supla-docker/.env
docker exec -it supla-db mysql -u supla --password=$DB_PASSWORD
Widziałeś ten temat?
SOP 2023 :heavy_check_mark:
SOP 2024 :heavy_check_mark:
Czekam na kolejne Supla Offline Party :upside_down_face:
🧩: 🔑cz->b ⛴️+ila
Top
User avatar
fracz
Posts: 2342
Joined: Fri Oct 28, 2016 10:56 pm
Location: Kraków
Has thanked: 4 times
Been thanked: 6 times

Post

Kolego masz złe hasło do bazy danych. Jeśli to jest świeża instancja i nic tam jeszcze nie ma to zatrzymaj kontenery i usuń cały katalog var/mysql (to usunie dane).

Pytanie dlaczego zgubiłeś hasło...?
Top

Return to “FAQ / Jak to zrobić”