Hi @zexoni70 

Thanks for posting in our business forum.

zexoni70 wrote

Dear @Clive_A , thanks.

 

I also noticed two more bugs, so I will tell you that your technicians know what they are about.

 

The first problem with the latest firmware is with the NTP servers for the correct time and the problem occurs again when the device is rebooted and then it simply won't update the correct time from the NTP server, but Google servers must be entered in the NTP fields and only then the device is updated at the correct time.

 

Another problem may have been noticed by your technician, which is that after the reboot of the device and when all the lights come on and the system is active, it takes at least 45 seconds to access the device locally.

Otherwise if an attempt is made to access the device before those 45 seconds pass then access is not possible for some reason.

 

Best regards!

 

 

 

 

 

 

 

 

 

 

 

NTP was this way all the time. It is not a bug. The saved time and config are on the cache. Not in the storage. This was answered several times before on the forum.

The bootup time is expected. It maintains a baseline time and takes more time if you have more settings.

Dear @Clive_A,

ok, and hank you for your replay.

Dear @Clive_A,

yesterday I installed the latest firmware  SG3428X(UN)_V1.30_1.30.2 Build 20240920 that was released on 15.11.2024 and the problem of remote access via https://public ip address: port number is still not solved and exists.

I have set everything correctly and as it should be, HTTPS is enabled and the port number is entered and assigned, but the device simply cannot be accessed remotely...

Have your technicians even tried remotely accessing the device with this latest firmware installed?

Regards.

 

Hi @zexoni70 

Thanks for posting in our business forum.

zexoni70 wrote

Dear @Clive_A,

 

yesterday I installed the latest firmware  SG3428X(UN)_V1.30_1.30.2 Build 20240920 that was released on 15.11.2024 and the problem of remote access via https://public ip address: port number is still not solved and exists.

 

I have set everything correctly and as it should be, HTTPS is enabled and the port number is entered and assigned, but the device simply cannot be accessed remotely...

 

Have your technicians even tried remotely accessing the device with this latest firmware installed?

 

Regards.
 

 

Can you show us a video of the problem persists?

You reported this problem and we located the issue by testing and fixed by the way we think. We tested it as well before we released it.

If this persists, please provide a video on your test and port forward and etc. Our test and dev will take a look.