EN admin_guide troubleshooting_save_errors

Troubleshooting Save Errors

Sometimes when creating or editing records in MagnusBilling, clicking Save may not complete the operation successfully. This can happen in any module, such as Users, Rates, Trunks, DIDs, Alarms, Providers, Campaigns, and others.

Before investigating further, always make sure your MagnusBilling installation is running the latest available version.

Update MagnusBilling First

Many issues are fixed in new releases. Before opening a support ticket, update MagnusBilling to the latest version and test again.

If the problem persists after updating, continue with the troubleshooting steps below.

Open Browser Developer Tools

The most effective way to identify save-related issues is by inspecting the browser's Developer Tools.

Google Chrome

Press:

F12

or

Ctrl+Shift+I

Microsoft Edge

Press:

F12

or

Ctrl+Shift+I

Mozilla Firefox

Press:

F12

or

Ctrl+Shift+I

Safari

Enable the Developer menu and press:

Option+Command+I

Analyze the Network Tab

1. Open the Network tab.
2. Leave Developer Tools open.
3. Click Save in MagnusBilling.
4. Locate the request generated by the action.

Verify:

• HTTP Status Code
• Request URL
• Request Parameters
• Response Body

Common HTTP Status Codes

Code	Description
200	Request processed successfully
400	Invalid or missing data
401	Authentication problem
403	Permission denied
404	Resource not found
500	Internal server error

Analyze the Console Tab

Open the Console tab and check whether any JavaScript errors appear when clicking Save.

Examples:

• Uncaught TypeError
• SyntaxError
• Failed AJAX request
• ExtJS component errors

Check Server Logs

If the request returns HTTP 500, inspect the web server logs.

Apache:

tail -f /var/log/apache2/error.log

CentOS/RHEL:

tail -f /var/log/httpd/error_log

Collect Information for Support

When opening a support request, provide:

• Screenshot of the Network tab
• Screenshot of the Console tab
• HTTP status code
• Complete server response
• MagnusBilling version
• Browser name and version

This information helps identify whether the issue is related to frontend validation, permissions, server-side errors, database constraints, or customizations.

See Also

• Update MagnusBilling
• Understanding HTTP 500 Errors
• Collecting Logs for Support

---

Documentation home · Documentation index · Edit this page