You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the interface to move an IP FO the api call doesn't take the responses into account, for example the “ { ‘message’: ‘There is some VMAC used and the destination server do not support VMAC’ }” which on the interface indicates that it's going well, whereas the api rejects the transfer directly.
API : /dedicated/server/{serviceName}/ipMove~POST
Steps To Reproduce
To reproduce this bug, you need a server that does not yet support VMAC transfer.
Then attempt to transfer an ip to the server
the server will just display that you have to wait a few minutes for the transfer and will display no error message
Expected Behavior
No response
What browsers are you using?
Chrome
Which devices are used?
Desktop
Additional information to add?
No response
The text was updated successfully, but these errors were encountered:
Have you already contacted our help centre?
Is there an existing issue for this?
Describe the bug
in the interface to move an IP FO the api call doesn't take the responses into account, for example the “ { ‘message’: ‘There is some VMAC used and the destination server do not support VMAC’ }” which on the interface indicates that it's going well, whereas the api rejects the transfer directly.
API : /dedicated/server/{serviceName}/ipMove~POST
Steps To Reproduce
To reproduce this bug, you need a server that does not yet support VMAC transfer.
Then attempt to transfer an ip to the server
the server will just display that you have to wait a few minutes for the transfer and will display no error message
Expected Behavior
No response
What browsers are you using?
Chrome
Which devices are used?
Desktop
Additional information to add?
No response
The text was updated successfully, but these errors were encountered: