Jump to content
Froxlor Forum

Adramyttium

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Adramyttium

  1. Quick question: Did you incorporate the fix in the latest froxlor release? I'm thinking of updating this week.
  2. Yeah, that exactly the thing I was confused about. From what I can see (and I certainly admit I may have missed something), the two IP/port combos I'm trying to delete don't seem to be used anywhere else in the system. One other thing I noticed recently, and I have no idea is this plays into my problem or not, but for the customer I created ('Practice') I created two test email addresses and corresponding accounts for both hosted domains on my froxlor. Then I decided against using email. I went in and first deleted each of the email accounts and then deleted email addresses themselves for
  3. I agree, total nonsense. That, along with the redirect issue, caused me to revisit the IP/ports and delete them, as they were unnecessary. Here are some shots of the settings.
  4. I have froxlor configured to use SSL with Let's Encrypt, and have the system set up to auto redirect to SSL (https) if the user tried to navigate to the froxlor admin with http. The problem: When froxlor redirects automatically to SSL, is attempt to do so using port 993, rather than port 443. As a result the page doesn't load. Originally, I set up only two IPs in froxlor, one for standard web hosting traffic (port 80), and one for SSL web traffic (port 443) At one point, I thought I'd use froxlor for email, so I created two additional IP entries for ports 143 and 993. Becau
  5. Okay. So I basically should only need an MX record in DNS pointing to the domain name, and it should work?
  6. I have set up my froxlor server for email. I have a domain that I'd like to test this out. I have set up my domain, "orangekarat.com". This is an email domain. I have created one email address with an associated email account and password. I have opened up ports 143 and 993 for IMAP messages in froxlor. Is this all I need to do, or are there other steps? In trying to use the account in a third-party email app, what configurations should I specify? Of course this is new to me, so if you have a guide you could recommend for my study, that would be awesome.
  7. I'm running Froxlor on Unbuntu 18.04 having installed the product via apt repository. I've successfully changed settings and run the necessary configurations. I chose to secure the froxlor webhost itself using Let's Encrypt. This was successful. I've also added a customer domain and secured that domain with SSL using a Let's Encrypt cert. So, the hostname of my froxlor webserver is 'admin.orangekarat.com.' SSL is enabled and Let's Encrypt encryption is working as expected. The customer domain is my personal domain, 'christopherdrew.com.' SSL is enabled and Let's Encrypt enc
  8. So I started over, patiently following all of the instructions. It's working brilliantly. Thank you so much for Froxlor. Great product.
  9. I'm going to scratch this attempt and start with a snapshot that includes LAMP. Question, if apache2 is already installed on the server, must I still run the configuration routine in Froxlor?
  10. Very interesting. I just tried restarting apache2 from the command line and, sure enough, it failed. I checked the service status: sudo systemctl status apache2.service ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: failed (Result: exit-code) since Sat 2020-02-22 17:47:15 UTC; 49s ago Process: 13800 ExecStop=/usr/sbin/apachectl stop (code=exited, status=1/FAILURE) Process: 1
  11. Well, I waited overnight for things to propagate, and I'm still getting the danged login screen. To try to further isolate the cause, I actually deleted the domain and the customer and decided to try again. So here is what I have: One domain with a single "A" @ DNS record pointing to the server IP address. I created a new customer in Froxlor. I added the domain to Froxlor (using domain.tld) The IP address is assigned to the domain using both ports 80 and 443. SSL redirect is off on 443 and I'm not using Let's Encrypt. Before clicking save, I checked the /var/
  12. Oh boy... As I said earlier, I'm pretty new to this stuff, but I know enough to know that I need a danged 'A' record on the domain.tld. So if I correct that and let the Let's Encrypt cron job run a few times, should that clear up the matter?
  13. No problem. I'll create a temp account for you with Sudo. I'll send you the credential via PM in a few.
  14. Yes, they are in /etc/apache2/sites-enabled One more question: When I was setting things up, I changed the apache2 document root from /var/www/html to /var/www. Would that have caused some kind of issue? (And thank you for your quick replies!)
  15. I'm totally new to this as well, and I'm experiencing a similar problem. Domains are going to the Froxlor login page. I've checked my DNS records and they are pointing to ipv4 addresses. The vhost files seems to be in place as expected (in /sites-enabled). The server itself is on a DigitialOcean and does not have ipv6 enabled. The files for the web domain seem to be in the correct document root directory. And yet, I get the login page. Any other ideas about what could check?
×
×
  • Create New...