Q: How to fix "COPY <<EOF ... no source files were specified" when building the Cypht Docker image from master?

The Dockerfile uses BuildKit heredoc syntax, which is not supported by the legacy `docker build` path. Use Buildx instead from the repository root: ```sh docker buildx build . --platform linux/amd64 -t dockerid/cypht:master docker ``` Replace `dockerid/cypht:master` with your preferred image name. If Buildx is not configured, create and select a builder first with `docker buildx create --use`.

Q: How do I fix Cypht scheduled emails failing with "Failed to authenticate to the SMTP server", undefined $smtpId, and HTML being sent as plain text?

This is a bug in Cypht 2.9.0's scheduled-send pipeline, not an SMTP credential problem. The scheduler does not initialize `$smtpId` when the message uses an `X-Profile-ID` SMTP profile, causing authentication to fail. Patching only that variable can make sending work, but the same pipeline may still build the message as `text/plain`, exposing HTML tags and logging `Undefined array key 1/2` in `modules/smtp/modules.php` on line 1680. Upgrade Cypht/Docker image to a build containing the fix for issue #1981, then recreate the container: `docker pull cypht/cypht:latest && docker compose up -d` (or use the first fixed release/tag instead of `latest`). Confirm scheduled messages are sent with the same SMTP profile and a `multipart/alternative`/`text/html` MIME structure. If you cannot upgrade immediately, use immediate send instead of scheduled send; a partial `$smtpId` patch alone is not sufficient.

Q: Why do Safari tests fail on Travis CI with BrowserStack and Selenium?

Safari tests often fail on Travis due to an issue with maximizing the browser window, likely from version differences in Selenium or BrowserStack environments. Workarounds: 1) Disable 'exit on error' for Safari tests to keep CI running (as done in this repo). 2) Locally, identify and code around the 5 consistently failing tests. Ensure consistent versions across local and CI environments.

Question 1

Why does Cypht log out immediately after login with 'invalid source origin' error in Docker?

Accepted Answer

This is a known bug in Cypht 2.12.2 where Origin validation fails when accessing Cypht directly via a LAN IP and non-standard port (e.g., http://192.168.1.240:8080), even when Host and Origin headers match. The session is created and then immediately destroyed.

**Fix:** Upgrade to Cypht 2.13.0, where this issue is resolved:
```bash
docker pull cypht/cypht:2.13.0
```

**Workaround for 2.12.2:** Disable the Origin check in your environment configuration (acceptable for LAN/VPN-only instances not exposed to the Internet):
```env
DISABLE_ORIGIN_CHECK=true
DISABLE_IP_CHECK=true
DISABLE_FINGERPRINT=false
```
Then restart the container. Note this disables a CSRF protection mechanism, so upgrading to 2.13.0 is the preferred solution.

Question 2

Why does Cypht Docker container fail with 'Unable to connect to database' when using SQLite?

Accepted Answer

The entrypoint script defaults to checking remote database connectivity if DB_HOST, DB_USER, or DB_PASS are not explicitly set, even when DB_DRIVER=sqlite. To force local SQLite, set these variables to empty strings in your container configuration: Environment=DB_HOST=, Environment=DB_USER=, Environment=DB_PASS=. This bypasses the remote connection attempts and uses the specified SQLite file.

Question 3

How to fix "COPY <<EOF ... no source files were specified" when building the Cypht Docker image from master?

Accepted Answer

The Dockerfile uses BuildKit heredoc syntax, which is not supported by the legacy `docker build` path. Use Buildx instead from the repository root:

```sh
docker buildx build . --platform linux/amd64 -t dockerid/cypht:master docker
```

Replace `dockerid/cypht:master` with your preferred image name. If Buildx is not configured, create and select a builder first with `docker buildx create --use`.

Question 4

How do I fix Cypht scheduled emails failing with "Failed to authenticate to the SMTP server", undefined $smtpId, and HTML being sent as plain text?

Accepted Answer

This is a bug in Cypht 2.9.0's scheduled-send pipeline, not an SMTP credential problem. The scheduler does not initialize `$smtpId` when the message uses an `X-Profile-ID` SMTP profile, causing authentication to fail. Patching only that variable can make sending work, but the same pipeline may still build the message as `text/plain`, exposing HTML tags and logging `Undefined array key 1/2` in `modules/smtp/modules.php` on line 1680. Upgrade Cypht/Docker image to a build containing the fix for issue #1981, then recreate the container: `docker pull cypht/cypht:latest && docker compose up -d` (or use the first fixed release/tag instead of `latest`). Confirm scheduled messages are sent with the same SMTP profile and a `multipart/alternative`/`text/html` MIME structure. If you cannot upgrade immediately, use immediate send instead of scheduled send; a partial `$smtpId` patch alone is not sufficient.

Question 5

Why do Safari tests fail on Travis CI with BrowserStack and Selenium?

Accepted Answer

Safari tests often fail on Travis due to an issue with maximizing the browser window, likely from version differences in Selenium or BrowserStack environments. Workarounds: 1) Disable 'exit on error' for Safari tests to keep CI running (as done in this repo). 2) Locally, identify and code around the 5 consistently failing tests. Ensure consistent versions across local and CI environments.

Cypht

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects