Management IP Address can be enabled by clicking on the “?” next to Hostname in WAN settings:
Service Provider Configuration via DHCP Option is only available at this moment for the partners or users who need to load a lot of devices with the same configuration before sending them to the field.
@RolandasR : Thank you! So that is intended to configure an external company Management Server’s public IP address (to avoid access from somewhere else)? Does this block incontrol servers then?
I was about to upgrade mine, standing by pending further info, thanks!
OK. I give up. What is a “Management IP Address for DHCP WAN”? Its not explained in the Release Notes and its not even mentioned in the 8.1.2 User Guide.
I installed this and immediately experienced the inability to connect to most of my WiFi network. After about a day troubleshooting this, the problem was isolated to the fact this revision does not work with VLANs. Rolling back to the previous 8.1.1 does not fix the problem. My guest, security and camera systems are down because of this. This is as serious a failure as it gets. What assistance does Peplink offer in fixing this?
We have some reference here :
It’s more to the IP address to manage the gateway device that running using different IP network for the management. 
Can you please open a ticket for us to further check on this ? Please ATTN the ticket to sitloongs
What device type…and what AP(s)?
i opened a ticket i have no cellular connectivity at all this is very frustating
This upgrade did not work out too well, at least in one instance:
Background:
An HD2 IP67 LTEA is located in a remote area, connected only by cellular (Verizon). It is connected to a B380 hub (SpeedFusion) and handles local servers, devices and Pepwave access points…
History & problem:
The device has been working flawlessly with FW 8.1.1.
An upgrade to FW 8.1.2 GA seemed to succeed, but some hours after the upgrade we observed that the unit no longer responded to WebUI logins (be it from WAN, SF or LAN), nor to UI access from InControl, nor did it report to InControl, nor did it respond to speed fusion speed tests from the B380 hub (the error there being “Error: Cannot connect to remote server at port 5000”) .
The response to a connection to the login URL (via a public IP address, the speedfusion connection or from a server on the LAN) is “System error” after the URL is directed from the base URL (https://router.xxx.com) to the usual landing path (https://router.xxx.com/cgi-bin/MANGA/index.cgi).
The unit continues to route correctly, and remote access via SF to device-local servers continues to function.
We have no direct, physical access to the device, so a local reboot or similar attempts to kick it back alive are not available to us.
With IC2 connection and WebUI connections both inoperative, we cannot get a diagnostic report nor turn on RA.
I can provide sample screenshots demonstrating things that work (the core functionality of routing and speedfusion connectivity) and those that don’t (IC2, WebUI via LAN, WAN, SF).
Suggestions?
Ticket submitted: 21050466
I have configured my Peplink Balance One Router via System Security settings to listen on HTTPS only using a specific Web Admin Port (e.g. 9000).
When I am using the Router’s URL only with HTTP in the browser (http://IP.IP.IP.IP:9000 instead of https://IP.IP.IP.IP:9000), I am receiving the following error message:
The plain HTTP request was sent to HTTPS port
nginx
I’d like to suggest to fix this by auto forwarding to HTTPs protocol.
@ckirch : mainly it was done for Starlink app dish management as described here
It allows to access external network using configured IP address instead of the main WAN IP.
It is not related to the Incontrol servers as the default gateway is being used for that matter.
I read that item and it raised more questions than it answered. To be fair, that item starts in the middle of the topic, not the beginning.
Is this feature is for Starlink only?
If not, what problem is it solving?
It is indeed for Starlink. Possibly could apply to other gateway manufacturers who don’t use standard IP of 192.168.100.1 but have a custom mobile app that allows you to manage the device.
My understanding of it.
I installed 8.1.2 and it does not seem to be stable. I get random reboots and my wifi has dropped to nothing. I have a balance one. How do find 8.1.1 to downgrade?
@Wayne_Goldstein, I am curious whether the problem will happen to the previous firmware version. You may reboot your Balance One to the previous firmware at System > Reboot.
@ckirch, that’s been considered and the improvement has been registered in the wishlist We should see it in the next major release 
I found it by searching for archive. I uploaded the previous version and all issues went away. I suggest that there is a problem with the 8.1.2
Tried to upgrade last night and what a disaster. Half my Wifi devices never reconnected. Another 1/4 were flapping up and down. I know this because I monitor my smart home devices with Nagios and I could see them going up and down. Tried to reboot, adjust broadcast settings, to no avail.
I rolled back and the 1/4 that were flapping came back, but the other half are still down… I dread having to go around reconnecting all these devices again.
I’m curious what happened… did the firmware upgrade somehow change the SSIDs (like the MAC associated with them) and that’s why the devices couldn’t reconnect is because technically it changed despite the name and keys being the same?
Can someone please look into this?
