Bug: RUTX50 DHCP Server - Unable to create static entry

Networking Solutions Issue
1

Hi,

I have a RUTX50 using the latest available firmware (7.21.2).

I have existing DHCP Reservations on my RUTX50…some of these devices are connected to the network at the present time, some are not.

I have connected a new device via WiFi, and it has successfully been allocated an IPv4 address from the DHCP pool.

I want to a Static Address for this new device so using Network > DHCP > Static Leases have selected the new device, then the desired IP address.

When I click ‘Save & Apply’ an “An unexpected error occurred” message is displayed and the new Static Lease doesn’t save.

This seems to be a bug…is anyone else experiencing the same issue with this firmware version ?

Thanks in advance.

3

Hi, @griffo ,

Welcome to Teltonika Community!

Thank you for reporting this issue. To help us investigate further, could you please clarify a few things:

  1. How many static leases do you currently have configured? Is it possible you’ve hit a limit?
  2. Does the error occur when adding a lease manually (by typing the MAC address) rather than selecting from the dropdown?
  3. Have you tried a different browser or cleared your cache before attempting to save?
  4. Did a reboot resolve or change the behavior at all?
  5. Could you share any relevant entries from System Logs (Status > System Logs) captured right after the error appears?
  6. Was this working on a previous firmware version?

Your answers will help us determine whether this is a firmware bug or a configuration issue.

Looking forward to your response.

Best regards,
V.

4

Hello Vilius,

I have the same issue, to answer your questions: I have RUTX50 RUTX_R_00.07.21.3

  1. How many static leases do you currently have configured? Is it possible you’ve hit a limit? 0

  2. Does the error occur when adding a lease manually (by typing the MAC address) rather than selecting from the dropdown? Yes

  3. Have you tried a different browser or cleared your cache before attempting to save? Yes

  4. Did a reboot resolve or change the behavior at all? No

  5. Could you share any relevant entries from System Logs (Status > System Logs) captured right after the error appears?

880 2026-04-02 12:12:56 DHCP Network Info Leased 192.168.123.97 IP address for client 3e:64:7c:de:22:b1 - b2-nuc in LAN

Was this working on a previous firmware version? Yes

5

Greetings, @osevera,

I hope you’re doing well,

Could you please create a separate topic for your issue? This will help us avoid any confusion and ensure that we can provide you with a solution tailored specifically to your case.

Thank you for your understanding.

Best regards,
V.

6

Hello Vilius,

I did create a new topic althou the symptoms are the same. See

7

Dear @griffo, my thread for a temporary fix.