Hello,
Some customers reported that an error is returned when they are editing an alias from our control panel.
I was able to reproduce the issue from both our control panel and also from SM's web admin.
Please note that while an error is returned, the change is still applied to the alias. Still, we need the error returned by the API to be fixed as it perturbates our users.
Examples:
This happens when you add or remove a target for an existing alias From the GUI:
And same action from our control panel (API calls and response debug):
>>> Oct 27 04:14:18 <<<
Request
POST /api/v1/settings/domain/alias HTTP/1.1
Connection: close
Accept-encoding: gzip, deflate
User-Agent: Ace_Http_Client
Authorization: Bearer youwishtoknow
Content-Type: application/json
Content-Length: 49
{"alias":{"name":"bernardo","allowSending":true}}
>>> Oct 27 04:14:18 <<<
Response
HTTP/1.1 400 Bad Request
Content-length: 83
Content-type: application/json; charset=utf-8
Content-security-policy: default-src 'self';frame-src 'self' *.youtube.com youtu.be *.smartertools.com docs.google.com;script-src * 'unsafe-inline';font-src * 'unsafe-inline' data:;$
X-frame-options: SAMEORIGIN
X-xss-protection: 1; mode=block
X-content-type-options: nosniff
X-robots-tag: noindex
X-powered-by: ARR/3.0
X-powered-by: ASP.NET
Strict-transport-security: max-age=0
Date: Sun, 27 Oct 2024 03:14:18 GMT
Connection: close
{"message":"Object reference not set to an instance of an object.","success":false}
>>> Oct 27 04:14:28 <<<This seems to be a recent issue introduced in some recent builds as the complaints started to emerge this weekend.
Kind regards