March 7, 2018 at 7:10 am #36113
i am migrating monyog from windows to debian 9. I want to bind the monyog service to loopback device only that it is not reachable over standard port. I can’t find a way in the documentation. Is there anything I can do?
March 7, 2018 at 9:47 am #36120
Sibin A SModerator
Can you please elaborate more. Please tell have you migrated Monyog from Windows to Debian?
Also, tell exactly what happened that should have not, and what does not happen that should?
For migrating Monyog, please verify if you have followed the steps below,
Install Monyog on the new system and copy the following folders from your old machine to the new machine,
The above files including the ‘Data’ folder can be found at the location in Windows OS,
Ensure the MONyog service is stopped on the old machine before taking the backup of the files and also stop the Monyog service in the new machine before importing the backup to avoid conflicts/inconsistency between the files.
You may also refer the FAQ, here
April 10, 2018 at 10:02 am #36126
Sorry for my late reply. I haven’t seen my thread after I created it (and I did it twice), so I thougt the forum isn’t working.
I didn’t migrate monyog from windows to debian with the data inculude. I just did a clean installation on debian 9. I use nginx as suggested to have ssl support.
What I want is to bind the built in webservice to localhost/127.0.0.1 device so it is not accessible over network. I block it by iptables but this can be difficult to debug sometimes.
May 15, 2019 at 1:48 pm #36167
I need to do this as well. Running an unencrypted service listening on all ports is a violation of federal security policy. Just blocking with iptables does not suffice because the service still shows as listening and local scanners see that. This is a very simple feature that every product should have — how do I add bind-address: localhost ?
You must be logged in to reply to this topic.