Jack
EACCES: permission denied, mkdir (LibreChat)
When trying to upload a file in LibreChat (with a volume at /app/client/public/images), I'm getting the following error.
2024-05-21 16:05:37 error: [/files/images] Error processing file: EACCES: permission denied, mkdir '/app/client/public/images/65ab45969a4fd2a833f2b2c3'
2024-05-21 16:05:37 error: [/files/images] Error deleting file: ENOENT: no such file or directory, unlink '/app/client/public/images/65ab45969a4fd2a833f2b2c3/Huskies Illinois.jpg'
2024-05-21 16:05:37 error: [/files/images] Error processing file: EACCES: permission denied, mkdir '/app/client/public/images/65ab45969a4fd2a833f2b2c3'
2024-05-21 16:05:37 error: [/files/images] Error deleting file: ENOENT: no such file or directory, unlink '/app/client/public/images/65ab45969a4fd2a833f2b2c3/Huskies Illinois.jpg'
8 replies
Repetitive error creating Odoo service (+ template)
KeyError: 'ir.http'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/odoo/http.py", line 2189, in __call__
response = request._serve_db()
File "/usr/lib/python3/dist-packages/odoo/http.py", line 1769, in _serve_db
exc.error_response = self.registry['ir.http']._handle_error(exc)
File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 213, in __getitem__
return self.models[model_name]
KeyError: 'ir.http'
2024-02-27 20:21:33,989 7 INFO railway werkzeug: 10.10.10.12 - - [27/Feb/2024 20:21:33] "GET /admin HTTP/1.1" 500 - 2 0.007 0.022
2024-02-27 20:21:40,044 7 ERROR railway odoo.sql_db: bad query:
SELECT latest_version
FROM ir_module_module
WHERE name='base'
ERROR: relation "ir_module_module" does not exist
LINE 3: FROM ir_module_module
^
2024-02-27 20:21:40,060 7 WARNING railway odoo.addons.base.models.ir_cron: Tried to poll an undefined table on database railway.
2024-02-27 20:21:43,073 7 ERROR railway odoo.sql_db: bad query:
SELECT latest_version
FROM ir_module_module
WHERE name='base'
ERROR: relation "ir_module_module" does not exist
LINE 3: FROM ir_module_module
^
2024-02-27 20:21:43,074 7 WARNING railway odoo.addons.base.models.ir_cron: Tried to poll an undefined table on database railway.
KeyError: 'ir.http'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/odoo/http.py", line 2189, in __call__
response = request._serve_db()
File "/usr/lib/python3/dist-packages/odoo/http.py", line 1769, in _serve_db
exc.error_response = self.registry['ir.http']._handle_error(exc)
File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 213, in __getitem__
return self.models[model_name]
KeyError: 'ir.http'
2024-02-27 20:21:33,989 7 INFO railway werkzeug: 10.10.10.12 - - [27/Feb/2024 20:21:33] "GET /admin HTTP/1.1" 500 - 2 0.007 0.022
2024-02-27 20:21:40,044 7 ERROR railway odoo.sql_db: bad query:
SELECT latest_version
FROM ir_module_module
WHERE name='base'
ERROR: relation "ir_module_module" does not exist
LINE 3: FROM ir_module_module
^
2024-02-27 20:21:40,060 7 WARNING railway odoo.addons.base.models.ir_cron: Tried to poll an undefined table on database railway.
2024-02-27 20:21:43,073 7 ERROR railway odoo.sql_db: bad query:
SELECT latest_version
FROM ir_module_module
WHERE name='base'
ERROR: relation "ir_module_module" does not exist
LINE 3: FROM ir_module_module
^
2024-02-27 20:21:43,074 7 WARNING railway odoo.addons.base.models.ir_cron: Tried to poll an undefined table on database railway.
3 replies
Errors deploying Attendize (event manager)
> [base 2/5] RUN apt-get update && apt-get install -y wait-for-it libxrender1:
0.652 Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [586 kB]
0.762 Get:6 http://nginx.org/packages/mainline/debian buster InRelease [3607 B]
0.802 Get:7 http://deb.debian.org/debian buster/main amd64 Packages [7909 kB]
0.952 Get:8 http://deb.debian.org/debian buster-updates/main amd64 Packages [8788 B]
1.076 Err:4 https://packages.sury.org/php buster InRelease
1.076 The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
1.351 Get:9 http://nginx.org/packages/mainline/debian buster/nginx amd64 Packages [60.6 kB]
3.420 W: GPG error: https://packages.sury.org/php buster InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
3.420 E: The repository 'https://packages.sury.org/php buster InRelease' is not signed.
-----
Dockerfile:5
-------------------
3 | # Base image with nginx, php-fpm and composer built on debian
4 | FROM wyveo/nginx-php-fpm:php74 as base
5 | >>> RUN apt-get update && apt-get install -y wait-for-it libxrender1
6 |
7 | # Set up code
-------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y wait-for-it libxrender1" did not complete successfully: exit code: 100
> [base 2/5] RUN apt-get update && apt-get install -y wait-for-it libxrender1:
0.652 Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [586 kB]
0.762 Get:6 http://nginx.org/packages/mainline/debian buster InRelease [3607 B]
0.802 Get:7 http://deb.debian.org/debian buster/main amd64 Packages [7909 kB]
0.952 Get:8 http://deb.debian.org/debian buster-updates/main amd64 Packages [8788 B]
1.076 Err:4 https://packages.sury.org/php buster InRelease
1.076 The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
1.351 Get:9 http://nginx.org/packages/mainline/debian buster/nginx amd64 Packages [60.6 kB]
3.420 W: GPG error: https://packages.sury.org/php buster InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
3.420 E: The repository 'https://packages.sury.org/php buster InRelease' is not signed.
-----
Dockerfile:5
-------------------
3 | # Base image with nginx, php-fpm and composer built on debian
4 | FROM wyveo/nginx-php-fpm:php74 as base
5 | >>> RUN apt-get update && apt-get install -y wait-for-it libxrender1
6 |
7 | # Set up code
-------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y wait-for-it libxrender1" did not complete successfully: exit code: 100
3 replies
Migrate dockerfile commands to start command
Migrating use of a repo with a Dockerfile for my Wordpress template, however encountered issues on the way.
Dockerfile:
Start command (doesnt respond after "Restarting Apache httpd web server: apache2"):
RUN echo "ServerName 0.0.0.0" >> /etc/apache2/apache2.conf
RUN echo "DirectoryIndex index.php index.html" >> /etc/apache2/apache2.conf
# Set the maximum upload file size directly in the PHP configuration
RUN echo "upload_max_filesize = $SIZE_LIMIT" >> /usr/local/etc/php/php.ini
RUN echo "post_max_size = $SIZE_LIMIT" >> /usr/local/etc/php/php.ini
CMD ["apache2-foreground"]
RUN echo "ServerName 0.0.0.0" >> /etc/apache2/apache2.conf
RUN echo "DirectoryIndex index.php index.html" >> /etc/apache2/apache2.conf
# Set the maximum upload file size directly in the PHP configuration
RUN echo "upload_max_filesize = $SIZE_LIMIT" >> /usr/local/etc/php/php.ini
RUN echo "post_max_size = $SIZE_LIMIT" >> /usr/local/etc/php/php.ini
CMD ["apache2-foreground"]
/bin/bash -c "echo 'ServerName 0.0.0.0' >> /etc/apache2/apache2.conf && echo 'DirectoryIndex index.php index.html' >> /etc/apache2/apache2.conf && echo 'upload_max_filesize = 50M' >> /usr/local/etc/php/php.ini && echo 'post_max_size = 50M' >> /usr/local/etc/php/php.ini && chown -R www-data:www-data /var/www/ && a2enmod rewrite && apache2ctl configtest && service apache2 restart"
/bin/bash -c "echo 'ServerName 0.0.0.0' >> /etc/apache2/apache2.conf && echo 'DirectoryIndex index.php index.html' >> /etc/apache2/apache2.conf && echo 'upload_max_filesize = 50M' >> /usr/local/etc/php/php.ini && echo 'post_max_size = 50M' >> /usr/local/etc/php/php.ini && chown -R www-data:www-data /var/www/ && a2enmod rewrite && apache2ctl configtest && service apache2 restart"
24 replies
Postgres database, "Can't reach database server"
Checked old posts, of which suggested sleeping the project before start, and/or adding
repo: https://github.com/ghostfolio/ghostfolio/tree/main
Image: https://hub.docker.com/r/ghostfolio/ghostfolio (used)
?connect_timeout=300
to the end of the DATABASE_URL
variable would resolve the issue, did not, the project is continuing to erorr with the following console output.
yarn run v1.22.19
$ yarn database:migrate && yarn database:seed && node main
$ prisma migrate deploy
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"
Error: P1001: Can't reach database server at `postgres.railway.internal`:`5432`
Please make sure your database server is running at `postgres.railway.internal`:`5432`.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this comman
yarn run v1.22.19
$ yarn database:migrate && yarn database:seed && node main
$ prisma migrate deploy
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"
Error: P1001: Can't reach database server at `postgres.railway.internal`:`5432`
Please make sure your database server is running at `postgres.railway.internal`:`5432`.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this comman
51 replies
Just got an odd building error, for reference
Was re-building a deployment from upstream github commit for a server project when I encountered this, trying to redeploy now redeploying worked.
#1 [internal] load .dockerignore
#1 DONE 3.9s
#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1699920194
#3 ERROR: failed to authorize: failed to fetch anonymous token: Get "https://ghcr.io/token?scope=repository%3Arailwayapp%2Fnixpacks%3Apull&service=ghcr.io";: net/http: TLS handshake timeout
-----
> [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1699920194:
-----
Dockerfile:1
-------------------
1 | >>> FROM ghcr.io/railwayapp/nixpacks:ubuntu-1699920194
2 |
3 | ENTRYPOINT ["/bin/bash", "-l", "-c"]
-------------------
ERROR: failed to solve: ghcr.io/railwayapp/nixpacks:ubuntu-1699920194: failed to authorize: failed to fetch anonymous token: Get "https://ghcr.io/token?scope=repository%3Arailwayapp%2Fnixpacks%3Apull&service=ghcr.io";: net/http: TLS handshake timeout
Error:
Docker build failed
#1 [internal] load .dockerignore
#1 DONE 3.9s
#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1699920194
#3 ERROR: failed to authorize: failed to fetch anonymous token: Get "https://ghcr.io/token?scope=repository%3Arailwayapp%2Fnixpacks%3Apull&service=ghcr.io";: net/http: TLS handshake timeout
-----
> [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1699920194:
-----
Dockerfile:1
-------------------
1 | >>> FROM ghcr.io/railwayapp/nixpacks:ubuntu-1699920194
2 |
3 | ENTRYPOINT ["/bin/bash", "-l", "-c"]
-------------------
ERROR: failed to solve: ghcr.io/railwayapp/nixpacks:ubuntu-1699920194: failed to authorize: failed to fetch anonymous token: Get "https://ghcr.io/token?scope=repository%3Arailwayapp%2Fnixpacks%3Apull&service=ghcr.io";: net/http: TLS handshake timeout
Error:
Docker build failed
9 replies
Errors deploying nocodb
[Nest] 11 - 12/01/2023, 3:56:20 PM ERROR [ExceptionHandler] KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Error: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
at NcConfig.create (/usr/src/app/docker/main.js:2:1811775)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1286537)
at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:369:37)
at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:65:34)
at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:144:24)
at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:70:13)
at async Injector.loadProvider (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:97:9)
at async /usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:56:13
at async Promise.all (index 3)
at async InstanceLoader.createInstancesOfProviders (/usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:55:9)
(node:9) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
╔══════════════════════════════════════════════════════════════════════════════╗║ ║║ EXCEPTION OCCURED!! in PGClient @ createDatabaseIfNotExists ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ MESSAGE: ║║ getaddrinfo ENOTFOUND postgres.railway.internal ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ CODE: ║║ ENOTFOUND ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ STACK: ║║ Error: getaddrinfo ENOTFOUND postgres.railway.internal ║║ at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ ║║ ║╚═══════════════════════
[Nest] 11 - 12/01/2023, 3:56:20 PM ERROR [ExceptionHandler] KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Error: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
at NcConfig.create (/usr/src/app/docker/main.js:2:1811775)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1286537)
at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:369:37)
at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:65:34)
at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:144:24)
at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:70:13)
at async Injector.loadProvider (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:97:9)
at async /usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:56:13
at async Promise.all (index 3)
at async InstanceLoader.createInstancesOfProviders (/usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:55:9)
(node:9) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
╔══════════════════════════════════════════════════════════════════════════════╗║ ║║ EXCEPTION OCCURED!! in PGClient @ createDatabaseIfNotExists ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ MESSAGE: ║║ getaddrinfo ENOTFOUND postgres.railway.internal ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ CODE: ║║ ENOTFOUND ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ STACK: ║║ Error: getaddrinfo ENOTFOUND postgres.railway.internal ║║ at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ ║║ ║╚═══════════════════════
10 replies
documenso docker build failed
#12 1.868 npm WARN config production Use `--omit=dev` instead.
#12 3.225 Error: Could not find a schema.prisma file that is required for this command.
#12 3.225 You can either provide it with --schema, set it as `prisma.schema` in your package.json or put it into the default location ./prisma/schema.prisma https://pris.ly/d/prisma-schema-location
#12 ERROR: process "/bin/bash -ol pipefail -c npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build" did not complete successfully: exit code: 1
-----
> [stage-0 8/10] RUN --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/marketing/next/cache,target=/app/apps/marketing/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/web/next/cache,target=/app/apps/web/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-node_modules/cache,target=/app/node_modules/.cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ee/next/cache,target=/app/packages/ee/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/lib/next/cache,target=/app/packages/lib/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ui/next/cache,target=/app/packages/ui/.next/cache npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build:
1.868 npm WARN config production Use `--omit=dev` instead.
3.225 Error: Could not find a schema.prisma file that is required for this command.
3.225 You can either provide it with --schema, set it as `prisma.schema` in your package.json or put it into the default location ./prisma/schema.prisma https://pris.ly/d/prisma-schema-location
-----
Dockerfile:24
-------------------
22 | # build phase
23 | COPY . /app/.
24 | >>> RUN --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/marketing/next/cache,target=/app/apps/marketing/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/web/next/cache,target=/app/apps/web/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-node_modules/cache,target=/app/node_modules/.cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ee/next/cache,target=/app/packages/ee/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/lib/next/cache,target=/app/packages/lib/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ui/next/cache,target=/app/packages/ui/.next/cache npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build
25 |
26 |
-------------------
ERROR: failed to solve: process "/bin/bash -ol pipefail -c npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build" did not complete successfully: exit code: 1
Error: Docker build failed
#12 1.868 npm WARN config production Use `--omit=dev` instead.
#12 3.225 Error: Could not find a schema.prisma file that is required for this command.
#12 3.225 You can either provide it with --schema, set it as `prisma.schema` in your package.json or put it into the default location ./prisma/schema.prisma https://pris.ly/d/prisma-schema-location
#12 ERROR: process "/bin/bash -ol pipefail -c npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build" did not complete successfully: exit code: 1
-----
> [stage-0 8/10] RUN --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/marketing/next/cache,target=/app/apps/marketing/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/web/next/cache,target=/app/apps/web/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-node_modules/cache,target=/app/node_modules/.cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ee/next/cache,target=/app/packages/ee/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/lib/next/cache,target=/app/packages/lib/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ui/next/cache,target=/app/packages/ui/.next/cache npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build:
1.868 npm WARN config production Use `--omit=dev` instead.
3.225 Error: Could not find a schema.prisma file that is required for this command.
3.225 You can either provide it with --schema, set it as `prisma.schema` in your package.json or put it into the default location ./prisma/schema.prisma https://pris.ly/d/prisma-schema-location
-----
Dockerfile:24
-------------------
22 | # build phase
23 | COPY . /app/.
24 | >>> RUN --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/marketing/next/cache,target=/app/apps/marketing/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-apps/web/next/cache,target=/app/apps/web/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-node_modules/cache,target=/app/node_modules/.cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ee/next/cache,target=/app/packages/ee/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/lib/next/cache,target=/app/packages/lib/.next/cache --mount=type=cache,id=s/1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926-packages/ui/next/cache,target=/app/packages/ui/.next/cache npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build
25 |
26 |
-------------------
ERROR: failed to solve: process "/bin/bash -ol pipefail -c npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build" did not complete successfully: exit code: 1
Error: Docker build failed
15 replies
Railway CLI postgresql not installed?
I installed the CLI and postgresql on my computer to use pgloader to migrate a mysql db to postgres for performance and cost sakes, but trying to run
railway connect Postgres
returns "psql must be installed to continue".5 replies
Formbricks Template error (upon redeployment w/ SMTP setup)
error getting environment TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: Error: connect ECONNREFUSED ::1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '::1',
port: 3000
}
}
Failed to get first environment of user; signing out
error getting environment TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: Error: connect ECONNREFUSED ::1:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '::1',
port: 3000
}
}
Failed to get first environment of user; signing out
12 replies