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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:16:11] ERROR: Got unexpected response from the API: Service not enabled
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database
Error: P1013: The provided database string is invalid. empty host in database URL. Please refer to the documentation in https://www.prisma.io/docs/reference/database-reference/connection-urls for constructing a correct connection string. In some cases, certain characters must be escaped. Please check the string for any illegal characters.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
I saw a closed issue with the same report, (#33) but that user did not have the Maria DB addon running. It is running in my instance.
Is there another configuration change needed somewhere?
The text was updated successfully, but these errors were encountered:
Log is this:
I saw a closed issue with the same report, (#33) but that user did not have the Maria DB addon running. It is running in my instance.
Is there another configuration change needed somewhere?
The text was updated successfully, but these errors were encountered: