ConfigServer Community Forum

Thank you ConfigServer for this new feature!

This feature provides a HTML UI to csf and lfd, without requiring a control panel or web server.

Working 100%

How can I acces to CSF config with this feature ?
No cPanel, no webmin, ...

Thanks in advance !

Ougogo,

Please see the readme file at this link : configserver[dot]com/free/csf/readme.txt

Scroll to item # 23 (23. Integrated User Interface Feature)

Make sure to enable the ui interface and on which port you would like to use it and add your IP address to /etc/csf/ui/ui.allow

Thanks... I'm a little bit stupid sorry.

But where can I configure the port ? I've try https://<my_ip>:6666 Like in example, but no results.

I've this error :
Erreur 312 (net::ERR_UNSAFE_PORT) : Erreur inconnue

I've disable "testig_mod" open "6666" port, restart csf/lfd, write my IP in "ui.allow".

Hi,

This is usually a browser error like Google Chrome would do it. Try IE or FireFox for the fun of it.

Firefox and IE "The connection failed".

Please, help me...

ougogo wrote:Firefox and IE "The connection failed".

Please, help me...

Yeah, configuring the web interface to let you connect can be a real pain.

- Make sure these are set in csf.conf:

UI = "1"
UI_PORT = "6666"

- Put your IP address (that you are connecting from) in this file:
/etc/csf/csf.allow

- Put your IP address (that you are connecting from) in this file too:
/etc/csf/ui/ui.allow

Finally restart the lfd service (on Debian, 'service lfd restart'). You should be able to connect on port 6666. Note that too many incorrect password login attempts to this web interface will mean your IP gets banned. In that case, you'll need to edit this file to remove yourself from the ban list:
/etc/csf/ui/ui.ban

The ui.ban file overrides ui.allow, so it doesn't matter if your IP is in ui.allow; you'll still be banned this way.

Oh yeah, and don't use Chrome. It doesn't trust you to connect on most ports and appears to be designed for idiots.

Resolve with that :

To fix this, you have to explicitly allow the unsafe port when you start up chrome.

Right click on your chrome icon that you use to launch chrome, and click properties.

The textbox that says "Target" will look something like this (your username obviously)
C:\Users\dougt\AppData\Local\Google\Chrome\Application\chrome.exe

To allow ports 81,84 and 87, change it to:
C:\Users\dougt\AppData\Local\Google\Chrome\Application\chrome.exe --explicitly-allowed-ports=81,84,87

Thanks

ougogo wrote: ↑13 Jan 2013, 23:35 Resolve with that :

To fix this, you have to explicitly allow the unsafe port when you start up chrome.

Right click on your chrome icon that you use to launch chrome, and click properties.

The textbox that says "Target" will look something like this (your username obviously)
C:\Users\dougt\AppData\Local\Google\Chrome\Application\chrome.exe

To allow ports 81,84 and 87, change it to:
C:\Users\dougt\AppData\Local\Google\Chrome\Application\chrome.exe --explicitly-allowed-ports=81,84,87

Thanks

or just change CSF UI port over 8000. 8080, 8081 are working perfectly (tested) with no problem in chrome

larryl79 wrote: ↑11 Apr 2018, 14:52or just change CSF UI port over 8000. 8080, 8081 are working perfectly (tested) with no problem in chrome

Why should your browser dictate which port you put your web interface on? I don't want it on a standard port. Defense in depth.