pearcy
Explore posts from serversEmail Configuration Fails with "550 5.7.1 Relaying Denied"
I'm encountering an issue with sending emails from Ghost CMS hosted on Railway. Despite having correct SMTP settings with Mailgun, I consistently receive the following error in the logs:
550 5.7.1 Relaying denied
Background:
I've verified my SMTP settings with Mailgun by testing them directly using curl for both ports 587 (TLS) and 465 (SSL), and both tests were successful.
Here are the environment variables I have set in Railway for Ghost CMS:
curl Test Script:
I used the following curl test script to confirm that Mailgun is processing emails correctly:
Can you help determine why Ghost CMS, with the same SMTP settings, fails with the relaying denied error while the curl test works fine? Is there any specific configuration or network restriction on Railway that might be causing this issue?
11 replies
MySQL Deployment Fails
I'm encountering issues with a MySQL instance running on Railway, which seems to be affecting my deployment. I tried another instance and getting the same error. Using the built-in deploy path - Create / Database / Add MySQL
17 replies
Ghost CMS email config
I’m running into an issue with Ghost CMS where users are unable to sign up for my newsletter due to an email configuration problem. Here’s the setup and what I’ve tried so far:
#### Steps Taken:
1. Created Subdomain in Mailgun:
- Subdomain:
Mailgun Logs: #### Question: - Is using environment variables in Railway instead of
mg.domain.com
2. DNS Configuration:
- Added MX, TXT, and CNAME records to my Namecheap registrar.
3. DNS Check & Verification:
- All records passed DNS checks and are verified in Mailgun.
4. Email Configuration in Railway:
- I added the email settings as Railway environment variables instead of using config.production.json (I don’t believe I have access to the config file due to deployment via a Railway Docker image).
Environment Variables:
Reference:
https://ghost.org/docs/config/
5. Mailgun Configuration Verification:
- I used swaks to confirm that my Mailgun SMTP settings are correct.
- A test email was successfully sent and received via my terminal.
Mailgun Logs: #### Question: - Is using environment variables in Railway instead of
config.production.json a workable approach for Ghost CMS email configuration?
Any insights or suggestions would be greatly appreciated.6 replies
Deploying Ghost on Railway from GitHub Repo
Hey everyone,
I’m working on self-hosting a Ghost CMS using the Ghost Starter repo from my GitHub: https://github.com/TryGhost/Starter.
Setup:
1. Project: Ghost CMS, based on the Starter theme, hosted on Railway.
2. Deployment method: Self-hosting on Railway, pulling the source code directly from my GitHub repo.
Issue:
I’m facing a deployment issue during the
- I was able to deploy using Railway’s templates but need to deploy from my GitHub repo to allow for editing and updates. Any advice or insights would be appreciated! Thanks in advance!
yarn install --frozen-lockfile step. Here’s what the logs show:
It seems the lockfile needs to be updated, but the install process is forced to use a frozen lockfile, causing the build to fail.
package.json snippet
What I Need Help With:
- Given that I’m using the starter Ghost CMS repo, do I need to update the lockfile, or is there a better approach to avoid this error?
- Am I missing anything in my setup for deploying on Railway when self-hosting without Docker?- I was able to deploy using Railway’s templates but need to deploy from my GitHub repo to allow for editing and updates. Any advice or insights would be appreciated! Thanks in advance!
6 replies
WWasp-lang
•Created by pearcy on 1/11/2024 in #🙋questions
Unable to access the Dashboard as an admin user
When I spin up a open-saas repo (https://github.com/wasp-lang/open-saas.git) everything works swimmingly except I am unable to access to the Dashboard as an admin user.
-- running locally, Docker Postgres, dev
env changes:
// app/.env.server
[email protected]
// app/main.wasp
isAdmin Boolean @default(true)
Expected behavior:
After these env changes, I signup and should have access to the Dashboard.
-- there is nothing in my account in nav so enter /admin directly in the URL.
If I change all the values to "false", I can get access to the Dashboard but when I go back to account or demo-app it routes me to the login screen.
// app/main.wasp
```
route AdminRoute { path: "/admin", to: DashboardPage }
page DashboardPage {
authRequired: false,
component: import Dashboard from "@client/admin/pages/DashboardPage"
}11 replies