ssl certificate ai issue
pratyush-0022
HOBBYOP

a month ago

just bought the pack asked your ai to deploy website, it just rewrite the codes shared and end the conversation with limit over except no ssl certificate relecting

Solved$10 Bounty

Pinned Solution

Try removing the domain from Railway and add it back after ~10-15 mins. Update DNS record as necessary.

34 Replies

pratyush-0022
HOBBYOP

a month ago

hi


Railway
BOT

a month ago

All your services are deployed successfully, and your Railway-generated domains (.up.railway.app) automatically include SSL certificates with no additional setup required. You can access any of your services over HTTPS right now. If you need SSL on a custom domain you own, you would first add that domain to your service under the service's Settings, then configure DNS at your registrar.


Status changed to Awaiting User Response Railway about 1 month ago


Railway

All your services are deployed successfully, and your Railway-generated domains (`.up.railway.app`) automatically include SSL certificates with no additional setup required. You can access any of your services over HTTPS right now. If you need SSL on a custom domain you own, you would first add that domain to your service under the service's Settings, then configure DNS at your registrar.

pratyush-0022
HOBBYOP

a month ago

need help fraud ai job performed instead of deploy write the unnecery codes


Status changed to Awaiting Railway Response Railway about 1 month ago


Railway
BOT

a month ago

Your services are all deployed and running, and SSL is active on all your .up.railway.app domains. The "limit over" message you encountered is your AI Agent usage limit, which is separate from your deployments. Your Agent usage this billing cycle is $5.17, which exceeded the default $5 hard limit, so the agent session ended. You can view and adjust this limit at your usage page by clicking "Update limits" - you can raise it to continue using the agent, or set it to $0 to disable agent usage entirely and prevent further agent charges.


Status changed to Awaiting User Response Railway about 1 month ago


pratyush-0022
HOBBYOP

a month ago

so you mean now there is no limit left


Status changed to Awaiting Railway Response Railway about 1 month ago


pratyush-0022
HOBBYOP

a month ago

i want refund raise my concern to real agent and ask him to refund the amount and fix agent limit and connect ssl certificate to custom domain, also in that amount free services ask agent ton deploy the website


Railway
BOT

a month ago

Your AI Agent hit the default $5 hard limit for this billing cycle, so the agent is paused until the cycle resets. Your deployments and services are completely unaffected and keep running normally. To re-enable the agent sooner, go to your usage page, click "Update limits", and raise the Agent hard limit above your current spend, or set it to $0 if you want to disable the agent entirely and avoid further agent charges.


Status changed to Awaiting User Response Railway about 1 month ago


pratyush-0022
HOBBYOP

a month ago

no you are not getting it check i made the recharge now only for the deployment and it wasted my recharge unnecessory by writing my own application recodes for no purpose


Status changed to Awaiting Railway Response Railway about 1 month ago


pratyush-0022
HOBBYOP

a month ago

no you are not getting it check i made the recharge now only for the deployment and it wasted my recharge unnecessory by writing my own application recodes for no purpose


Railway
BOT

a month ago

Your $5 payment was for the Hobby plan subscription, and your services are all deployed and running with SSL active. The AI Agent usage ($5.17) drew from your plan's included credit and is billed separately from compute. Agent usage is considered authorized when you use the feature, so we're unable to refund it, but you can set the Agent hard limit to $0 at your usage page to prevent any further agent charges. If you'd like to request a refund for the plan subscription itself, you can do so from Workspace Settings > Billing under Billing History.


Status changed to Awaiting User Response Railway about 1 month ago


pratyush-0022
HOBBYOP

a month ago

no it is not like that check

image.png

Attachments


Status changed to Awaiting Railway Response Railway about 1 month ago


Railway
BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway about 1 month ago


You need to add a TXT record at _railway-verify.www.aai-core.com. If you're using the API, you can find the content for it from the verificationToken property under status.


pratyush-0022
HOBBYOP

a month ago

are yoiu an railway agent


If "agent" refers to the AI agent, then no.


pratyush-0022
HOBBYOP

a month ago

service agent or random interupter


I'm a moderator. That still doesn't change the fact that you need to add a TXT record to the domain target I mentioned above.


pratyush-0022
HOBBYOP

a month ago

connect me to service agent


This thread won't be escalated to the team as it isn't an issue related to the platform, nor is it widespread.

As mentioned above, you need to add the TXT record.


pratyush-0022
HOBBYOP

a month ago

check that i have added the domain manually connected the dns and now there is no option to view all that, unnecesarry limit used how should i provide you the txt you tell me, web is running on local host but not on railway after making the payment also

image.png

Attachments


I checked, and the TXT record isn't present. Check the domains section in your service settings. If there's a button that allows you to show DNS records, you'll be able to find the TXT from there. If not, try removing the domain and add it back.


pratyush-0022
HOBBYOP

a month ago

shall i provide that to you please share the list of requirements.


What do you mean by list of requirements?


pratyush-0022
HOBBYOP

a month ago

only txt is required or something else is required for the certificate

i have checked the txt its available


pratyush-0022
HOBBYOP

a month ago

i have configured all the setting of custom domain, still web is not reflecting on the domain, if its becouse of ssl please forward the request on priority and if due to any other kindly please inform


Your TXT records needs to be on _railway-verify.www.


pratyush-0022
HOBBYOP

a month ago

corrected, kindly please resolve the issue


pratyush-0022

i have configured all the setting of custom domain, still web is not reflecting on the domain, if its becouse of ssl please forward the request on priority and if due to any other kindly please inform

a month ago

It might take up to 24 hours to verify your domain's DNS records.

Just give it some time if you have successfully added both CNAME and TXT records to your domain registrar


pratyush-0022
HOBBYOP

a month ago

thanks a lot for a positive response, will notify you if didn't in timeline


pratyush-0022
HOBBYOP

a month ago

it has been not resolved yet kindly resolve the issue on priority

image.png

Attachments


Your CNAME record should be pointing to what Railway provided when you added your custom domain. It should not point to the pregenerated domain.

Also, it may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.


pratyush-0022
HOBBYOP

a month ago

i have already updated the dns with required configuration as per the railway, rest you can share by your self to i will addon them all, its approx 48 hrs certificate has not been issued.


Try removing the domain from Railway and add it back after ~10-15 mins. Update DNS record as necessary.


pratyush-0022
HOBBYOP

a month ago

did still same, kindly please resolve the issue on priority, i am using paid service


pratyush-0022
HOBBYOP

a month ago

resolved thanks a lot


Status changed to Solved 0x5b62656e5d about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...