Jump to content
Froxlor Forum

User

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About User

  • Rank
    Newbie
  1. You answered my questions perfectly. In this question I was talking about restricting access to admin interface per each user so we would ask the costumer from what public IP address he will access the admin console for initial login and then he could add or remove IP addresses from where he could access it. I guess we can do htaccess or vpn like you said but if you could do that via web console it would be a great addition... for feature descriptions I will ask on the forums as I go. If I decide to only run nginx are there any significant drawbacks for web hosting on froxlor? Like we would only use http, https and let's encrypt basic web hosting features. You can do that without apache on froxlor? Are there any significant advantages for running apache with froxlor? Thanks again...
  2. Hello, We are looking to configure froxlor and we have some basic questions. What is the most common/recommended setup for froxlor? Is it to run each service (dns, web, ftp...) on different servers or having all services on one? I guess it all depends on the scale of hosting you are doing. We want to setup froxlor to be able to scale to many costumers and be resilient to network attacks. Is it possible to assign each service their own ip address?. For example we would have for costumers running their website on one ip address on ports 80/443 and 21 for ftp. Then we would have admin console on another ip address and dns on another and so on. I know you can assign specific IP addresses to specific costumers web pages but I did not see that you can also assign specific ip for ftp access for a costumer? Are access lists so costumers can allow (for example ftp access just from their own home ip address) planed at all?. Same goes for admin console. Is it possible to restrict ip access and users can easily edit it? Is it common to expose admin console to the world? How confident are you that people will not be able to break through? I know you have 2FA for user accounts and with login timeout and strong passwords we should be safe right? Also is there any plan to create a detailed documentation explaining each froxlor feature with clear examples (I mean each option you can select in froxlor settings)? I know you are answering every question on forum, have https://github.com/Froxlor/Froxlor/wiki and have quite good descriptions near each option but there is really no detailed explanation for each feature with clear examples. This is really what separates a good open source project to an amazing one. I guess if you make the documentation too good then people will not need your help so that's a draw back I guess. Thank you for reading and answering my questions.
  3. Hello, Is it possible to configure froxlor, to edit dns records on dns server, that is not running on the same virtual machine that froxlor web editor is running? Thank you for your answer.
  4. Hello, We have control over our private and public network (servers and network equipment) and we would like to run froxlor behind a (hardware) firewall. Is there any technical reason why do you not allow private networks to be used for running froxlor? Currently we are running IIS web-server with private network setup inside and ip address translation via firewall to public network on the outside. Also if you add to the virtual machine private network and setup web server to install froxlor it will allow you to complete the installation with private ip but you will not be able to add any additional private addresses. Maybe you need to add some additional checks while doing preinstall prerequisites if you do not want to allow private networks to be used with froxlor. Thank you for the answer. I have some other questions that I will ask in another topic.
×
×
  • Create New...