You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Kong in a docker swarm I had set the KONG_PG_PASSWORD and KONG_PG_USER but I continued to receive:
2017/09/12 18:10:52 [verbose] saving serf shell script handler to /usr/local/kong/serf/serf_event.sh
2017/09/12 18:10:52 [verbose] SSL enabled, no custom certificate set: using default certificate
2017/09/12 18:10:52 [verbose] default SSL certificate found at /usr/local/kong/ssl/kong-default.crt
2017/09/12 18:10:52 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
2017/09/12 18:10:52 [verbose] admin SSL certificate found at /usr/local/kong/ssl/admin-kong-default.crt
2017/09/12 18:10:52 [verbose] running datastore migrations
2017/09/12 18:10:52 [verbose] could not start Kong, stopping services
2017/09/12 18:10:52 [verbose] leaving serf cluster
2017/09/12 18:10:52 [verbose] stopped services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: /usr/local/share/lua/5.1/kong/cmd/start.lua:21: [postgres error] could not get current migrations: [postgres error] FATAL: password authentication failed for user "kong"
stack traceback:
[C]: infunction'error'
/usr/local/share/lua/5.1/kong/cmd/start.lua:34: infunction'cmd_exec'
/usr/local/share/lua/5.1/kong/cmd/init.lua:88: infunction</usr/local/share/lua/5.1/kong/cmd/init.lua:88>
[C]: infunction'xpcall'
/usr/local/share/lua/5.1/kong/cmd/init.lua:88: infunction</usr/local/share/lua/5.1/kong/cmd/init.lua:45>
/usr/local/bin/kong:7: infunction'file_gen'
init_worker_by_lua:40: infunction<init_worker_by_lua:38>
[C]: infunction'pcall'
init_worker_by_lua:47: infunction<init_worker_by_lua:45>
However, running psql with the username and password all works fine.
I was able to realize on my own the issue was that my password had a special character within it:
one of -=!@#$%^&*() more specifically I had # mid way through my password and kong was unable to use the password properly.
After removing any special characters (which tbh keeps me from making my pw more secure) I am able to connect and run kong.
I was unable to find any documentation on this so I decided to leave this here.
Additional Details & Logs
Kong version (0.10.3)
Postgres version (9.6)
The text was updated successfully, but these errors were encountered:
jeremills
changed the title
Kong 0.10.3 won't start with "special characters" in password (fix)
Kong 0.10.3 won't start with "special characters" in password
Sep 12, 2017
"KONG_VERSION=0.14.1" also have this probleam, my pg password contain #,when migration,have the error:
Error:
/usr/local/share/lua/5.1/kong/cmd/migrations.lua:37: [postgres error] could not retrieve current migrations: [postgres error] FATAL: password authentication failed for user "kong"
Summary
Running Kong in a docker swarm I had set the
KONG_PG_PASSWORD
andKONG_PG_USER
but I continued to receive:However, running psql with the username and password all works fine.
I was able to realize on my own the issue was that my password had a special character within it:
one of
-=!@#$%^&*()
more specifically I had#
mid way through my password and kong was unable to use the password properly.After removing any special characters (which tbh keeps me from making my pw more secure) I am able to connect and run kong.
I was unable to find any documentation on this so I decided to leave this here.
Additional Details & Logs
0.10.3
)9.6
)The text was updated successfully, but these errors were encountered: