Failed to connect to MOD cloud

I’m getting the message “Failed to connect to MOD cloud” with the mouse hovering over the update button, and the plugins view only shows the installed plugins (the “installed only” button is unchecked). I haven’t changed anything since last time I connected it a few weeks ago.

I’ve tried several times today with a few hours and reboots in between and always get the same issue.

The browser console shows internal server errors from api.moddevices.com:

Failed to load resource: the server responded with a status of 500 (Internal Server Error)
?v=1.6.2.614:152 MOD authentication failed
stats:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
jquery-1.9.1.min.js?v=1.6.2.614:4 GET https://api.moddevices.com/v2/lv2/plugins?text=&summary=true&image_version=1.6.2.614&stable=true&_=1552176656957 500 (Internal Server Error)
send @ jquery-1.9.1.min.js?v=1.6.2.614:4
ajax @ jquery-1.9.1.min.js?v=1.6.2.614:4
searchAll @ cloudplugin.js?v=1.6.2.614:353
JqueryClass.$.fn.(anonymous function) @ modgui.js?v=1.6.2.614:1180
search @ cloudplugin.js?v=1.6.2.614:193
JqueryClass.$.fn.(anonymous function) @ modgui.js?v=1.6.2.614:1180
options.open @ cloudplugin.js?v=1.6.2.614:127
dispatch @ jquery-1.9.1.min.js?v=1.6.2.614:2
v.handle @ jquery-1.9.1.min.js?v=1.6.2.614:2
trigger @ jquery-1.9.1.min.js?v=1.6.2.614:2
(anonymous) @ jquery-1.9.1.min.js?v=1.6.2.614:3
each @ jquery-1.9.1.min.js?v=1.6.2.614:2
each @ jquery-1.9.1.min.js?v=1.6.2.614:2
trigger @ jquery-1.9.1.min.js?v=1.6.2.614:3
open @ window.js?v=1.6.2.614:138
$.fn.window @ window.js?v=1.6.2.614:198
toggle @ window.js?v=1.6.2.614:174
$.fn.window @ window.js?v=1.6.2.614:198
(anonymous) @ window.js?v=1.6.2.614:101
dispatch @ jquery-1.9.1.min.js?v=1.6.2.614:2
v.handle @ jquery-1.9.1.min.js?v=1.6.2.614:2
_super.bugsnag @ buy-button-storefront.js?v=1.6.2.614:7433
jquery-1.9.1.min.js?v=1.6.2.614:4 GET https://api.moddevices.com/v2/devices/nonce?_=1552176656959 500 (Internal Server Error)
send @ jquery-1.9.1.min.js?v=1.6.2.614:4
ajax @ jquery-1.9.1.min.js?v=1.6.2.614:4
Desktop.authenticateDevice @ desktop.js?v=1.6.2.614:357
Desktop.getDeviceShopToken @ desktop.js?v=1.6.2.614:1769
(anonymous) @ buy-button-storefront.js?v=1.6.2.614:5665
init @ buy-button-storefront.js?v=1.6.2.614:5664
createComponent @ buy-button-storefront.js?v=1.6.2.614:6180
(anonymous) @ desktop.js?v=1.6.2.614:1812
Promise.then (async)
Desktop.createCart @ desktop.js?v=1.6.2.614:1811
(anonymous) @ desktop.js?v=1.6.2.614:1787
Promise.then (async)
(anonymous) @ desktop.js?v=1.6.2.614:1785
Desktop.fetchShopProducts @ desktop.js?v=1.6.2.614:1783
searchAll @ cloudplugin.js?v=1.6.2.614:333
JqueryClass.$.fn.(anonymous function) @ modgui.js?v=1.6.2.614:1180
search @ cloudplugin.js?v=1.6.2.614:193
JqueryClass.$.fn.(anonymous function) @ modgui.js?v=1.6.2.614:1180
options.open @ cloudplugin.js?v=1.6.2.614:127
dispatch @ jquery-1.9.1.min.js?v=1.6.2.614:2
v.handle @ jquery-1.9.1.min.js?v=1.6.2.614:2
trigger @ jquery-1.9.1.min.js?v=1.6.2.614:2
(anonymous) @ jquery-1.9.1.min.js?v=1.6.2.614:3
each @ jquery-1.9.1.min.js?v=1.6.2.614:2
each @ jquery-1.9.1.min.js?v=1.6.2.614:2
trigger @ jquery-1.9.1.min.js?v=1.6.2.614:3
open @ window.js?v=1.6.2.614:138
$.fn.window @ window.js?v=1.6.2.614:198
toggle @ window.js?v=1.6.2.614:174
$.fn.window @ window.js?v=1.6.2.614:198
(anonymous) @ window.js?v=1.6.2.614:101
dispatch @ jquery-1.9.1.min.js?v=1.6.2.614:2
v.handle @ jquery-1.9.1.min.js?v=1.6.2.614:2
_super.bugsnag @ buy-button-storefront.js?v=1.6.2.614:7433
jquery-1.9.1.min.js?v=1.6.2.614:4 GET https://api.moddevices.com/v2/lv2/plugins/featured?_=1552176656966 500 (Internal Server Error)

Dear @davidr,

I’ve opened a ticket with our support team. They will be reaching out to you soon.

Cheers!

Same here, and http://pedalboards.moddevices.com
not reachable.

yeah the database seems to be down. so no pedalboards and no api

Hey guys. Thanks for reporting this.
We got a small issue with our API server. It’s back to normal.

Let me know if you still see any problems.

All looks good now. Thanks.

Are there any issues with the server again? Since yesterday I’m getting the same message hovering the update button (Failed to connect to MOD cloud), and when I open the plugin store I also got this message: “Can’t authenticate with cloud to access plugin store”.

Hi @zeebout I just checked the servers and everything looks normal.

Can you double check and confirm if you’re still seeing issues? I’ve looked for recent reports of network outages in our cloud provider (AWS) but didn’t find anything.

I found it… It was a browser add-on (Privacy Badger) that blocked the domain api.moddevices.com. I allowed the domain and the problem was solved :smirk:

Thanks for checking the network reports anyway.

1 Like

Hey there,
So, I was trying to install some new plugins on my mod duo x. But I always get the emssage “Failed to connect to mod cloud”. Didn’t find any solution here thats working for me.
Can somebody please help?

@Konrad_Gerber we recently moved our domains (.moddevices.com) to a new registrar. The migration should have be seamless but it’s possible you had DNS query failures during that window.

Before we go into further (more complicated) debugging, can you please try this one more time and let me know if it works?

Hi there, thanks for the response.
I tried the procedure one more time now, and it failed again.
So what should I do now?

I started having the same issue, unfortunately. Network connection is stable, the device works as expected but I cannot update the plugins and also did not get notifications for new SW versions. Only thing unusual: zeroconf/avahi does not resolve modduo.local, but accessing the device directly via IP works. I’m on Opensuse 15.1, all updates installed, Duo and Laptop were rebooted as well. I manually updated to v18.2 on the Duo and this also went flawlessly. Any ideas what to try next?

send me a PM with your serial number, will take a look then.

Much appreciated! Message sent…

Hi @falkTX. @acunha … thanks for catching up. As per your message I checked the browser console logs and get this error:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.moddevices.com/v2/devices/nonce?_=1574153193866. (Reason: CORS request did not succeed).

… this gave me the idea that it might be one of the Firefox plugins. And indeed, disabling the Firefox Privacy Badger plugin fixes the network problems. Thanks for the heads up!

I replied here and not to your message to let others find this solution as well. It is quite a popular plugin and protects one’s browsing without much human intervention.

2 Likes

Thanks for sharing @eggsperde, I will add this information to out Troubleshooting page in the wiki!

3 Likes

Good idea!

1 Like