#Deploy problem

1 messages · Page 1 of 1 (latest)

narrow jetty
#

Hi

URGENT - Deployment Error: "Failed to register domain"

Hello,

I have a critical issue with my production application deployment:

🔴 PROBLEM:

  • Domain: transport.munchenexpress.eu
  • Deployment error: "Registration Failed - Failed to register domain"
  • Clients see "orange page" in "Meine Bestellungen" section
  • Fixed the bug locally, but cannot deploy to production

📋 TECHNICAL DETAILS:

  • DNS configured correctly: A record → 34.57.15.54
  • DNS propagated globally (verified with dnschecker.org)
  • Site loads at transport.munchenexpress.eu
  • Current deployment: express-delivery-52.emergent.host
  • Tried deployment WITH and WITHOUT custom domain - same error
  • Rollback doesn't work (Failed to rollback deployment)

🛠️ WHAT I TRIED:

  1. Deploy with custom domain → error
  2. Deploy without domain (empty field) → error
  3. Rollback to previous deployment → error
  4. Waited for DNS propagation → doesn't solve it

❗ IMPACT:

  • Production broken for 2 days
  • Clients cannot see their orders
  • Bug fixed locally, but cannot update production

🙏 WHAT I NEED:

  1. Investigation of "Failed to register domain" error
  2. Manual deployment of new build OR
  3. Access to previous deployment with data OR
  4. Any solution to update production

Please help urgently. Thank you!

Job ID: 57c09a12-c948-4c7c-b680-efba498c2552
Email: [email protected]
Domain: transport.munchenexpress.eu

ember cape
#

I have successfully linked your domain. Please check it on your end to confirm. Everything should now be working fine.

narrow jetty
#

Thank you

narrow jetty
#

Greetings! Again I have the same problem described above in the message. Please help me!

#

Job Id 842262de-da51-46a7-aad8-abf8d8498fea

#

@ember cape hi

night aspen
#

@narrow jetty simply unlink from previous deployment and link it again in your current deployment

narrow jetty
#

Thank You

cunning sparrow
#

still havent gotten an aswer almost 24 hours later

humble pine
#

I want to delete my data and create fresh record

narrow jetty
#

Hello,

I'm experiencing repeated MongoDB authentication failures during deployment, which is preventing my application from deploying to production.

Job ID: dispatch-hub-58
(or click the 'i' button in chat interface for complete Job ID)

Error Details:
[MONGODB_MIGRATE] Emergent managed Atlas connection failed, attempting user creation: failed to ping MongoDB: connection() error occurred during connection handshake: auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-1": (AuthenticationFailed) Authentication failed.

What I've tried:

  • Deploy with external MongoDB Atlas (my own cluster)
  • Deploy with MONGO_URL in .env
  • Deploy without MONGO_URL in .env
  • Created .emergent-config.yml
  • All 9 deployment attempts failed at [MONGODB_MIGRATE] step with the same authentication error

Questions:

  1. Is MongoDB managed service enabled for my account?
  2. Are there any known issues with MongoDB managed infrastructure?
  3. Can I use my external MongoDB Atlas instead of managed service?
  4. What configuration is required for successful deployment?

My preview environment works perfectly, but production deployment consistently fails at MongoDB migration step.

Thank you for your assistance.

Best regards

#

Job ID
e19dc4b0-3554-4830-a8c3-d445f4697226

soft remnantBOT
#

Hey thanks for sharing job ID, we are checking this

earnest jewel
#

I am experiencing a similar issue, and it’s unacceptable that there are so many people with the same problem and still no real solution or response from Emergent. My application is live and in production, with clients depending on it, and yet I have received no immediate support to resolve a problem that is clearly caused by the platform itself.

This is a serious situation. Having clients in production and facing platform-caused issues with zero prompt resolution is a disgrace. We need urgent answers and proper support—this cannot continue any longer.

soft remnantBOT
#

e19dc4b0-3554-4830-a8c3-d445f4697226 For this job, we can see the deployment is done successfully. Please linking http://transport.munchenexpress.eu/ to this job, please first unlink it from your older job: 4a6bd7eb-bc38-42de-8284-c5e1419f16a5

soft remnantBOT
#

Hey Calin

The domain is linked to your old job 4a6bd7eb-bc38-42de-8284-c5e1419f16a5 - you will have to unlink it from that job and then link it here. That should fix the issue

narrow jetty
#

Subject: URGENT: Please unlink custom domain from old job

Hi Emergent Support Team,

I need urgent help with custom domain registration.

Issue:
My custom domain transport.munchenexpress.eu cannot be linked to my current job because it's still linked to an old job.

Details:

  • Custom domain: transport.munchenexpress.eu
  • Old job (needs unlink): 4a6bd7eb-bc38-42de-8284-c5e1419f16a5
  • Current job (needs link): e19dc4b0-3554-4830-a8c3-d445f4697226

What I see:

  • When I try to link the domain, I get "Registration Failed - Failed to register domain"
  • Domain verification shows old IP addresses instead of current deployment

What I need:
Please UNLINK transport.munchenexpress.eu from old job 4a6bd7eb-bc38-42de-8284-c5e1419f16a5 so I can link it to current job e19dc4b0-3554-4830-a8c3-d445f4697226.

DNS Configuration:

  • A Record: transport.munchenexpress.eu → 34.57.15.54 (configured correctly)
  • DNS propagation: Complete (verified with multiple DNS checkers)

This is urgent for my production deployment. The application works perfectly on dispatch-hub-58.emergent.host but I need my custom domain working.

Thank you for your help!

Best regards,
Adrian (Calin

soft remnantBOT
#

Hey Adrian

You can unlink the job form your previous domain by yourself. Just go to deployed apps menu inthe home screen (next to recent taks), find your old deployment, and remove the domain from there. Then you will be able ot link to new domain

narrow jetty
#

Subject: Custom domain not routing - Need SSL & routing configuration

Hi Support Team,

I need help configuring my custom domain transport.munchenexpress.eu for my application.

Current Status:

  • Domain unlinked from old job 4a6bd7eb-bc38-42de-8284-c5e1419f16a5 ✓
  • Domain linked to current job e19dc4b0-3554-4830-a8c3-d445f4697226 ✓
  • DNS configured: A record → 34.110.232.196 ✓
  • Application works on: https://dispatch-hub-58.emergent.host

Problem:

What I need:
Please configure routing and SSL certificate for transport.munchenexpress.eu on job e19dc4b0-3554-4830-a8c3-d445f4697226.

The domain is linked in UI but routing/SSL not working.

Thank you!

Job ID: e19dc4b0-3554-4830-a8c3-d445f4697226
Domain: transport.munchenexpress.eu

narrow jetty
#

Please, please help.

tepid flumeBOT
#

@narrow jetty The domain is pointing to wrong ip which is this 34.110.232.196.

Please follow these steps to fix the issue:

Go to your domain's DNS settings.

Add two new A records with the following details:

Type: A

Name: @

Value: 162.159.142.117

TTL: 3600

Type: A

Name: @

Value: 172.66.2.113

TTL: 3600

Save your changes and wait a few minutes for DNS propagation.

Then, click on 'check status' button in the ui.

This should allow your domain to connect successfully.

narrow jetty
#

Hello,

My production app (transport.munchenexpress.eu) is not updating after 8+ deployments in the last 24 hours.

Issue:

Preview updates correctly ✅
Production runs old code ❌
Critical payment bug: Stripe charges 0.32 EUR instead of 31.65 EUR
Evidence:

Added debug logging in latest deploy
Debug logs appear in preview MongoDB ✅
Debug logs NOT in production MongoDB ❌
Proves production not using deployed code
Details:

Domain: transport.munchenexpress.eu
Preview: express-delivery-60.preview.emergentagent.com
Same MongoDB for both
Waited 30+ mins after each deploy
Request: Please investigate why production deployment isn't updating code. Blocking my launch today.

Job Id
0cfe9db9-1ea0-4061-b9ca-ad9644dfb232
URGENT - Deployment broken for transport.munchenexpress.eu - 8+ deploys failed - production not updating - need immediate help"
Thanks, Adrian

narrow jetty
#

Please, please help.

narrow jetty
#

,😥

knotty pilot
#

im having same problem with ssl seems emergent no longer supports www.

narrow jetty
#

@Rajdeep Please, Help

tepid flumeBOT
#

@narrow jetty can you help me navigate through the app and find out where the changes are not reflecting ?

narrow jetty
#

@Rajdeep

Hi, thank you for responding!

Issue: After 8+ deployments, production (transport.munchenexpress.eu) doesn't update with new code changes. Preview works perfectly.

Evidence:

Added debug logging code (stripe_debug collection) in latest deploys
Debug logs appear in preview MongoDB ✅
Debug logs DON'T appear in production MongoDB ❌
This proves production is running OLD code
Current problems:

Login works but Stripe charges 0.78 EUR instead of 77.68 EUR (price divided by 100)
After payment, redirects to preview URL instead of production domain
All fixes work in preview but not in production
What I need: Please check why custom domain (transport.munchenexpress.eu) doesn't receive code updates after deployment.

Technical details:

Custom domain: transport.munchenexpress.eu
Preview: express-delivery-60.preview.emergentagent.com
Both use same MongoDB: mongodb+srv://podarcalin9_db_user:[email protected]/fastcurier

Thank you!

#

0cfe9db9-1ea0-4061-b9ca-ad9644dfb232

#

Job Id

tepid flumeBOT
#

@narrow jetty please make a small video and share it with us as im not able to reproduce the issue

narrow jetty
narrow jetty
#

@Rajdeep Can you help me?

narrow jetty
#

😥😥😥

#

<@&1325936972023201885> @admin URGENT - Job blocked 30+ hours, no response from @Rajdeep, sent 2 videos, production broken, need immediate help. Job ID: 0cfe9db9-1ea0-4061-b9ca-ad9644dfb232

#

Need urgent management assistance

I have been experiencing issues with my deployment for over 30 hours. Job ID: 0cfe9db9-1ea0-4061-b9ca-ad9644dfb232

I have submitted 2 videos as requested

I have mentioned @Rajdeep several times

I have not received a response for several hours

Product in production is not working properly (e.g. Stripe charges less than it should)

I cannot launch my business

I have invested credits, but the problem remains

I need prompt support to continue using the platform

narrow jetty
#

HELP HELP HELP HELP

foggy leaf
#

this is kamran from emergent

#

are you available now?

#

@narrow jetty

#

we can connect and resolve issues with your app

narrow jetty
# foggy leaf are you available now?

"Hi Kamran!

Yes, I'm available. Thank you for reaching out!

Issue Summary: I cannot deploy to production (transport.munchenexpress.eu). The preview environment works, but I'm not 100% sure if everything is correctly fixed.

What we fixed in preview with E1 agent:This is a forked j...

Buy
right arrow

Hey Calin, Quick input needed :
Ask Question
Agent will continue working after your reply
Perfect Adrian! Iată un mesaj profesional pentru suport:

Mesaj pentru kamran:

"Hi Kamran!

Yes, I'm available. Thank you for reaching out!

Issue Summary: I cannot deploy to production (transport.munchenexpress.eu). The preview environment works, but I'm not 100% sure if everything is correctly fixed.

What we fixed in preview with E1 agent:

Critical Stripe payment bug (was charging 1% of actual amount - now fixed)
Payment confirmation page not displaying (now works)
Analytics dashboard showing wrong revenue split for company vs couriers (corrected)
Frontend .env configuration issue (fixed)
Current Status:

Preview environment: Changes applied and seem to work
Production: Not yet deployed - waiting to confirm everything is stable
My Concern: Since these were critical bugs affecting payments and revenue calculations, I want to make sure:

The fixes are correct before deploying to production
Re-deploy will work properly
Nothing will break in production
Can you please:

Review the changes we made (I can share details)
Confirm it's safe to Re-Deploy to production
Or help me verify everything works correctly
I have paying customers and can't afford more downtime. Need your expert eyes on this before I push to production.

Thank you for your help! Adrian"

foggy leaf
#

@narrow jetty can we connect now to resolve the issues?