Not using special characters in the password will do the trick, but you can use special characters in the API call as long as they are properly url encoded (or percentage encoded). For instance, if your password is 'gF&2H:', the '&' and ':' characters in the API call should be percentage encoded as follows:
Thank you Henk,
It worked when we tried a password without special characters.
Error 304 means that the user name does not exist or that the password is incorrect. There are other authentication reasons why the API might not be accessible, for instance when access to the server status info is blocked in the privileges settings, but those reasons generate other error codes.
If you are certain that your user name and password are correct then you should check if they contain special characters that require URL encoding. It is possible that a special character is not sent correctly to Diafaan SMS Server if it is not properly URL encoded.
I may have logged a topic in this regard already. I'll try and give as much information as possible.
We set up a Diafaan server as a Proof of Concept on a Windows 2022 server hosted on Oracle Cloud with a web connector running on port 443 with SSL and added firewall rules for inbound traffic.
We can access the web console from the internet and login with user names and passwords created by the admin user.
When trying to query the API using https://myserver.com/http/request-server-status?username=xxxxx&password=xxxxx the server returns ERROR:304 Authentication failed, check username and password.
The same error is received when trying to access the API locally.
Most Users Ever Online: 529
Currently Browsing this Page:
Guest Posters: 668
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1472