Hi Mohammad Ali,
Thanks for the report, and sorry for the trouble.
The “Connection Successful” message is a bit misleading here. It only means WSMS could reach the gateway without a hard error. It does not confirm that mdpanel returned your balance. The part that matters is “Credit: false”. That is mdpanel’s web service answering with no credit value, which is why your messages are not going out.
The mdpanel gateway in WSMS connects to mdpanel’s older SOAP web service. When the credit comes back as false while your balance is fine and your settings have not changed, it almost always means something changed on mdpanel’s side, not in WSMS. The usual causes are:
– mdpanel moved or retired that older web service (the API address changed).
– The API username or password was reset or expired. On many panels these API credentials are separate from your normal panel login.
– Your account’s access to the web service API was turned off.
Since it stopped only in the last few days with no change on your end, the fastest path is to check with mdpanel directly. Please ask them:
1. Is the SMS web service (API) still active for my account?
2. Are my current API username and password still valid for it, or do I need new ones?
3. Have you changed or moved the web service address recently?
If mdpanel confirms they moved to a new API address or a new method, share those details here and we will update the gateway to match their current service.
It also helps if you can tell us your WSMS version and PHP version, so we can rule out anything on the plugin side.
Best regards,
Hi,
Thank you for your detailed explanation.
At the same time, I’ve also been in contact with mdpanel support, but unfortunately I haven’t been able to get anywhere so far. Their responses don’t seem very technical, and they’ve only suggested basic troubleshooting steps without investigating the API or web service itself.
I’m using the Forminator integration in WSMS, and the issue started around two weeks ago. Since then, SMS notifications triggered by form submissions have stopped completely.
One thing that makes me think the connection isn’t being established at all is that these messages don’t even appear in the mdpanel dashboard as failed or rejected SMS. If the request were reaching their servers, I would expect to see at least a failed delivery record. Instead, nothing is logged on their side.
Regarding your questions:
- As far as I know, my API credentials have not changed.
- I haven’t been informed of any changes to the API endpoint.
- mdpanel support hasn’t confirmed whether the API has changed or whether API access has been disabled.
So, at this point, I can’t answer those questions positively. It does seem possible that they have changed something in their API or SOAP service, although I don’t have enough information yet to be certain.
For reference:
- WSMS version: 7.2.5 (latest free version)
- PHP version: 8.2.30
Please let me know if there’s anything I can do to help troubleshoot this further. If there are any debug logs I can enable, tests I can run, or files I can provide, I’d be happy to assist in narrowing down the cause.
Hi,
Just wanted to provide an update on this issue.
The problem has now been resolved by the mdpanel technical team, and SMS messages are working normally again.
Unfortunately, they didn’t explain what the root cause was, so I still don’t know exactly what was wrong.
Thank you for your time.
Hi Mohammad,
Thanks for the update, glad it’s working again.
Quick note: “Connection Successful” just means the plugin reached mdpanel. Before sending, WSMS checks your credit with them, and that came back “false”, so it stopped. That is why the fix was on their side and nothing showed in your dashboard.
If it happens again, ask them to confirm API access is enabled on your account. The WSMS side looked fine.
Best
