Device-mode not being set to No on virtual RouterOS in Proxmox environment

Hi,

I have recently purchased a MikroTik Licence (Level-4) for using with my Proxmox virtual environment. But I am unable to use Proxy on this Virtual RouterOS. Also unable to create PPTP, L2TP VPN server on my MikroTik.

My MikroTik Details Are given below:

MikroTik Model: x86
Package Version: v6.48.6
Licence Level: 4

Problem Type: PPTP, L2TP VPN server & client creating issue | Web Proxy not working & unable to run Web proxy under this MikroTik. I have tried the following:

I have already tried the device mode manual but the flagged option is not being set to No:
https://help.mikrotik.com/docs/display/ROS/Device-mode

Since the RouterOS is virtual how is it possible to press a button on the device? The device mode manual mentions:
“The device mode can be changed by the user, but remote access to the device is not enough to change it. After changing the device-mode, you need to confirm it, by pressing a button on the device itself, or perform a “cold reboot” - that is, unplug the power:”

The RouterOS is virtual and not a physical device, so therefore is it possible to set the option for Flagged to No?
Device mode.png
See attached files.

Any assistance will be much appreciated.

Thank you,

Ash
MikroTik error - Copy.png

Please make a supout.rif file and submit it in support portal:
http://help.mikrotik.com/servicedesk/servicedesk/

It will be very useful to see, what has triggered Flagged in your system.

After you make the file and send to us, you can remove the Flagged status by issuing a cold reboot to the virtual system (not system reboot command, but physical hard reset)

The supout.rif file can be found in support portal ticket ref: SUP-69872. If you are unable to locate the supout.rif file, then let me know.

Please let me know your thoughts and a workable solution?

Kind regards,
Ash

To exit the flagged state, you must perform the command “/system/device-mode/update flagged=no”.
The system will ask to either press a button, or issue a hard reboot (cut power physically or do a hard reboot of the virtual machine)

Although the system has disabled any malicious looking rules, which triggered the flagged state, it is crucial to inspect all of your configuration for other unknown things, before exiting the flagged state. If your system has been flagged, assume that your system has been compromised and do a full audit of all settings before re-enabling the system for use.