# Issues After Updating VitalPBX 4.5  — API Error on Login

**URL:** https://forums.vitalpbx.org/t/issues-after-updating-vitalpbx-4-5-api-error-on-login/5752
**Category:** VitalPBX
**Created:** [October 1, 2025, 5:23pm UTC](https://forums.vitalpbx.org/t/issues-after-updating-vitalpbx-4-5-api-error-on-login/5752 "2025-10-01T17:23:11Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Haytham\_Waheed](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/haytham_waheed/32/3776_2.png) [@Haytham\_Waheed](https://forums.vitalpbx.org/u/Haytham_Waheed)
#### Post date: [October 1, 2025, 5:23pm UTC](https://forums.vitalpbx.org/t/issues-after-updating-vitalpbx-4-5-api-error-on-login/5752/1 "2025-10-01T17:23:11Z")

</div>

Hi VitalPBX Team,

We’re running VitalPBX 4.5 with Sonata Suite. Everything was working fine until we performed an update via the GUI (`Add-ons > Update`) followed by a CLI update (`apt update`) as ecommended in several community posts.

After the update, we encountered multiple issues—most notably, login to the gui now shows connection insecure which affect WebRTC access as well and trying to update the HTTP server to use the correct certificate or any other item in the system throws the following error:

Exception: API Error: [POST] /events 404 - at file /usr/share/vitalpbx/www/includes/rest\_client.php on line 0

**Error Trace:**

1 /usr/share/vitalpbx/www/index.php:0 app\Core-\>run(…args); 2 /usr/share/vitalpbx/www/includes/app/Core.php:0 app\Core-\>\_authorization(…args); 3 /usr/share/vitalpbx/www/includes/app/Core.php:0 app\Core-\>\_validate2FA(…args); 4 /usr/share/vitalpbx/www/includes/app/Core.php:0 EventLogger\EventLogger-\>logInUser(…args); 5 /usr/share/vitalpbx/www/includes/components/EventLogger/EventLogger.php:0 EventLogger\EventLogger-\>\_addEvent(…args); 6 /usr/share/vitalpbx/www/includes/components/EventLogger/EventLogger.php:0 vitalpbx\rest\_client-\>post(…args); 7 /usr/share/vitalpbx/www/includes/rest\_client.php:0 vitalpbx\rest\_client-\>execute(…args);

It seems the system is trying to POST to `/events`, but the endpoint returns a 404. I am not sure if this is related to the EventLogger component or something else.

**Steps we’ve taken so far:**

- Ran `apt update && apt upgrade -y` and `vitalpbx --update`
- Rebooted the system
- Checked NGINX config (`nginx -t`) and reloaded it
- Restarted VitalPBX (`vitalpbx restart`)
- Verified file permissions (`chown -R asterisk:asterisk /usr/share/vitalpbx`)

Despite these steps, the error persists. We’d appreciate any guidance on:

- Whether this is a known issue with the latest update
- How to restore the `/events` endpoint or reconfigure Sonata Suite
- Any additional logs or diagnostics we should check

Thanks in advance for your help!

---

<div class="post-metadata">

### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)
#### Post date: [October 1, 2025, 5:25pm UTC](https://forums.vitalpbx.org/t/issues-after-updating-vitalpbx-4-5-api-error-on-login/5752/2 "2025-10-01T17:25:57Z")

</div>

You can try the following:

```auto
dpkg --configure -a
apt-get --reinstall install logger-core -y
systemctl restart nginx

```

---

<div class="post-metadata">

### Author: ![Haytham\_Waheed](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/haytham_waheed/32/3776_2.png) [@Haytham\_Waheed](https://forums.vitalpbx.org/u/Haytham_Waheed)
#### Post date: [October 2, 2025, 11:35am UTC](https://forums.vitalpbx.org/t/issues-after-updating-vitalpbx-4-5-api-error-on-login/5752/3 "2025-10-02T11:35:18Z")

</div>

Thanks Miguel so much, this really works.

---

<div class="post-metadata">

### Author: ![system](https://forums.vitalpbx.org/uploads/default/original/1X/672b458a1d454755270c2c16adc5316b641c3c6a.png) [@system](https://forums.vitalpbx.org/u/system)
#### Post date: [November 1, 2025, 11:35am UTC](https://forums.vitalpbx.org/t/issues-after-updating-vitalpbx-4-5-api-error-on-login/5752/4 "2025-11-01T11:35:20Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
