Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

MySQL cannot Reconnect app (using current MySQL app or the legacy app)

  • December 9, 2024
  • 7 replies
  • 74 views
S
Forum|alt.badge.img

Our MySQL app connections are showing Reconnect app messages, but any attempt to reconnect fails (using the same credentials we have used for years) with a “authentication failed: Authentication Error. Please reconnect your Database account.” error.    

Our active Zaps using a Legacy connection continue to work, but we cannot change the Zaps using the newest MySQL connection to use the MySQL legacy connections.  When we select the legacy app and connection name, it then says that connection is expired.

Our database is on GoDaddy.  We are able to make remote connections without issue from our locations.   

Our MySQL legacy app’s connections have worked for 6 years (only being updated for password changes).  Even the newest MySQL app’s connections were working without issue for 2 weeks.  

 

Should I delete my new MySQL app and try to change the Zaps using those connections back to the MySQL legacy app?

 

Best answer by strongholdfloors

Disregard.  It is resolved.  Last week, some of our GoDaddy products were changed and it affected the firewall to our databases.  Just spoke with them and got it resolved.

View original
Did this topic help you find an answer to your question?

7 replies

S
Forum|alt.badge.img

Disregard.  It is resolved.  Last week, some of our GoDaddy products were changed and it affected the firewall to our databases.  Just spoke with them and got it resolved.

ken.a
1 person likes this
  • ken.a
    ken.a
ken.a
Forum|alt.badge.img+6
  • ken.aZapier Staff
  • Zapier Staff
  • 6519 replies
  • December 10, 2024

That’s an amazing news ​@strongholdfloors! We’re glad to hear that the issue is now resolved!

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗

S
1 person likes this
  • S
    strongholdfloors
S
Forum|alt.badge.img

Issue is now occurring again.  GoDaddy keeps telling me they are not blocking the Zapier  IP Address (54.86.9.50), but all of my MySQL connections are failing (new app and Legacy).   Any scripts I normally run from my home office work fine making the connection to the same database, regardless of my IP address (I moved it around using my VPN).   

Is anyone else reporting any issues connecting to MySQL databases hosted by GoDaddy?   

 

 

S
Forum|alt.badge.img

Still having the issue.  Intermittently today, the connections have worked (between 1 PM and 1:15 PM EST).  Spoke with GoDaddy again and got it escalated.   Here is what I got back:

 

Thank you for contacting Support. I would like to thank you for your patience while we investigated this matter. Your request has been directed to our department for review. The provided IP address - 54.86.9.50 - is not being blocked or restricted on the host machine or network. We have also confirmed that the IP 54.86.9.50 is allow listed for connecting to the hostname p3plmcpnl488136.prod.phx3.secureserver.net and the IP Address 72.167.56.63. Additionally, we are not seeing connection attempts from the IP 54.86.9.50 on the server. With the available information, it appears that the Zapier AWS host is unable to reach our network vs being actively blocked.

 

Is there anyway for someone at Zapier to see if the problem is with the AWS host reaching our destination (database host):   p3plmcpnl488136.prod.phx3.secureserver.net and the IP Address 72.167.56.63

JammerS
Forum|alt.badge.img+6
  • JammerSZapier Staff
  • Zapier Staff
  • 2566 replies
  • December 11, 2024

Hi ​@strongholdfloors,

 

If you're facing connectivity issues between AWS IPs and external servers, Zapier can't directly monitor or resolve them but can review your Zap logs for insights. Contact the support team with affected Zap IDs and error messages for targeted help. Meanwhile, consider alternative connection methods, such as a different server or an intermediary service.

 

I hope this helps! Let me know if you have any other questions.

S
Forum|alt.badge.img

JammerS - Thanks for the response.   I am being assisted by Customer Escalations now. 

I was going to look into moving my database from GoDaddy, but if you have heard of any intermediary service that would apply, please let me know.  

 

ken.a
Forum|alt.badge.img+6
  • ken.aZapier Staff
  • Zapier Staff
  • 6519 replies
  • December 12, 2024

That’s great news ​@strongholdfloors! Thank you for looping back with an update here.

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗

Reply


Terms & Conditions