a month ago
Attachments
14 Replies
a month ago
Have you tried disconnecting and connecting again the repository?
a month ago
it doesn't show the updated name as an option on the list?
It does show it, but the problem now is that it doesn't seem to be listening for any events from GitHub, and the CI/CD pipeline has completely broken.
I've attached the full report; the problems started right after the rename.
a month ago
will bump this up to the team
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
for reference team: the OP has a .md file attached and has tried every common troubleshooting
1. Disconnect + reconnect the branch `main` at the Railway service level.
2. Disconnect + reconnect the Source Repo at the Railway service level.
3. Uninstalled the Railway GitHub App from the `noondra` org → reinstalled fresh via the Railway "Connect Repo" flow.
4. Granted the Railway App access to "All repositories" (instead of select).
5. Verified in GitHub (`/orgs/noondra/settings/installations`):
- Install exists, not suspended.
- Permissions include read/write to `actions, administration, checks, code, commit statuses, deployments, pull requests, workflows`.
- Repository access includes `noondra/noondra`.
6. After reinstall + reconnect, the Source Repo panel displays:
> **Source Repo**: `noondra/noondra` ✓
> **Branch connected to production**: ⚠️ **Bad credentials**
7. **Created a brand new Railway project** (separate from `31e55206-4ca4-4b42-a27b-5ff70f9461b6`) and attempted to connect `noondra/noondra` from scratch in that new project → **same "Bad credentials" / Bad Request error**.
8. Connecting a **different repo** (any other repo from the same `noondra` GitHub org) to either the existing project or a new project works completely normally — the error is specific to the string `noondra/noondra` as a source, not to our org, our GitHub App install, or our project state.a month ago
They have not given the Railway integration sufficient permissions.
a month ago
Can you take a screenshot of the installed GitHub app? Like the one below
Attachments
Sure!
Attachments
a month ago
Ack! Will be confirming what is the missing permission as your screenshot looks correct.
change it to all repository
and try to manually update the repo after sucessfull push
i also got that issue but it just a issue of endpoint of somthing mainly it works out same
lastly try to do chrome dev tools after successfull login to github to see what is wrong