Hi Wappers, Can anyone provide guidance/suggestions on why a produciton site fails when a Development site works perfectly? Using Wappler 6.8.0, dockerdesktop on windows I build a simple registration form to insert a few fields into a database. The local dev target works perfectly however the production target on digitalocean fails. The the produciton target displays all the pages successfully with working features such as navigation, slider etc. But when I click on the production server action forms submit button (with the debug flag on) all I get is a check mark in each of the input fields the form doesn't submit and after a while I get a status 500...A server error occured...enable the DEBUG flag even though the debug flag is enabled. Any guidance/suggestions would be appreciated. Thanks in advance!
Hi Mark,
Please post a screenshot of the remote target settings in Wappler.
Is the production site available on a public url?
Have you selected the Production target and that screenshot refers to such Production target? Take a whole Wappler screenshot if you're unsure
Thanks Apple, I learned you can control the Debug flag per target, when you think about it is a great feature. Unfortunatly my Status 500 is a timeout error. So something is "not" connecting on the remote prodx svr that is on the local dev svr. Any testing suggestions ?
The DO server settings look okay.
Is the database hosted on the same server as the web app? If the database is available on the same (local server), then it could be an issue with the Port Number. Try with Port 3306 if the database is setup in the same docker container.
It's best if you post the literal error you get, it contains more specific information that might be useful to aid diagnosis
Thx for helping with this, I agree it has to be an issue with the database connection. Publishing with the db port set at 3306 failed. I would appreciate any other troubleshooting suggestions you may have?
Thanks for helping with this, sorry you are correct, here is the complete error:
{
"status": "500",
"code": "ETIMEDOUT",
"message": "Connection timeout",
"stack": "Error: Connection timeout\n at SMTPConnection._formatError (/opt/node_app/node_modules/nodemailer/lib/smtp-connection/index.js:809:19)\n at SMTPConnection._onError (/opt/node_app/node_modules/nodemailer/lib/smtp-connection/index.js:795:20)\n at Timeout. (/opt/node_app/node_modules/nodemailer/lib/smtp-connection/index.js:237:22)\n at listOnTimeout (node:internal/timers:588:17)\n at process.processTimers (node:internal/timers:523:7)"
}
Any other troubleshooting suggestions would be appreciated.
The Port Number should be 9906, not 3306 as I mentioned earlier. Sorry, it was my mistake in suggesting the change to 3306.
Are you sending an email when the form is submitted? The error is showing SMTP connection error. Verify whether the SMTP server settings are correct (host, port, credentials etc.). If these are correct, then it could be due to DO blocking SMTP emails on Port 25, 465 and 587.
Thank you gentlemen, I disabled the Send mail step and the app works. 
So it was the send mail on port 587. I am using PostmarkApp to actually send the email. Searching now for options to send mail from a DigitalOcean Droplet to the PostmarkApp. Any suggestions you have would be welcomed. Thanks again!, I Love this Wappler Community 
Port 587 on DO for sending mail is fine, we use the same port, maybe your mail server not allowing the connection?
You're welcome, Mark. Glad that it is working now.
I haven't used Postmark for emails. If the email volume is not very high, then you can look at SMTP2GO. They offer upto 1000 emails per month in their free plan.
You can use port 2525 for Postmark
Good Day Wapplers,
Received a Love Note from DigitalOcean (DO) that I thought might be helpful to other Wapplers using DO:
"Thank you for getting in touch with DigitalOcean Support. I am Farwa and I will be assisting you today. We understand you have concerns regarding SMTP restrictions in place for your account.
Please note as of March 6, 2025, DigitalOcean continued the commitment to keep the internet a safe and secure place by blocking use of SMTP ports 465 and 587, in addition to the previously blocked port 25, on all Droplets to mitigate spam and abuse originating from our platform. This decision is part of our ongoing efforts to maintain the security of our network and the greater internet.
However, I have reviewed your request and removed the SMTP restriction on the account. You should now have the access you need."
I’m not sure what criteria they are using to approve unblocking ports but this is what we sent DO:
Our app requires an email confirmation to opt-in users. We provided DO with the domain we were using through the Postmarkapp.com that already had DKIM & DMARC configured & verified.
This took a little over 24 hours. Here is a link to a DO support page describing their “Droplet Limits” dated 26 Mar 2025. https://docs.digitalocean.com/products/droplets/details/limits/#limits"%20>Limits<a%20href="#limits"%20class="anchor%20has-fa"%20onclick="navigator.clipboard.writeText(window.location.origin%20+%20window.location.pathname%20+%20'#limits');"%20>%20<i%20class="fa-solid%20fa-link
Thank You @guptast @Apple @Cheese for jumping in with your expert guidance. I really appreciate your support.
I just Love this Wappler community!