Jump to content
Froxlor Forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral


About Nepstar

  • Rank
    Advanced Froxie
  1. Ganz simpel die Linux-Rechte auf Ordner wie auch Dateien... obwohl Besitzer und Gruppe rwx auf tmp und packages hatten, war es wohl notwendig, allen rwx (sprich 777) zu vergeben... Meiner Meinung nach keine sch?ne L?sung aber anders funktionierte es nicht...
  2. Problem wurde selber gel?st, war ein unglaublich dummer Fehler, aber nun ist es erledigt... sch?nes Wochenende Euch allen!
  3. Dann stellt das Forum ab, wenn hier nicht aktiv geholfen wird...
  4. Push... leider mangelt es an Unterst?tzung... :-(
  5. I took this solution, too: http://forum.froxlor.org/index.php?/topic/1641-ssl-zertifikate-aber-wie/#entry7881
  6. Current status: doesn't work. If I'll disable the SSL checkbox in IP/Port, Froxlor won't create a vhost for :443 anymore. I'm still checking for another way... please let me know if I understood sth wrong. Thanks. Edit: Where should I remove all certificate entries - in the global SSL configuration or in the IP/Port settings? ...without destroying the apache configuration of course.^^ Edit #2: When I'm already talking about those two configurations. Why does Froxlor contain two parts for defining the SSL certificates' paths and what's exactly the differences between those options? I got a bit confused and I don't like to apply changes before I don't know the details here... In the documentation I didn't find anything yet.
  7. Hi again & sorry for my delayed reply! Unfortunately: Invalid command '<if', perhaps misspelled or defined by a module not included in the server configuration My working solution: <IfModule mod_core.c> <If "%{SERVER_PORT} == '443'"> <IfModule mod_ssl.c> SSLEngine On SSLCertificateFile /etc/apache2/ssl/file.crt SSLCertificateKeyFile /etc/apache2/ssl/file.key SSLCACertificateFile /etc/apache2/ssl/file.pem SSLCertificateChainFile /etc/apache2/ssl/file.pem </IfModule> </If> </IfModule> I'll check the IP/Port part now and hope not to destroy anything... :-)
  8. Bei mir funktionierte es auch einmal sehr gut... ;-) Wenn ich mich richtig erinnere, spinnt es seit der Umstellung zu fcgid mit suExec... nur kann ich aktuell den Zusammenhang nicht daraus schliessen, Auch l?uft Froxlor selber unter dem www-User, nur die Kunden verwenden fcgid/suExec. Zu Deinen Fragen: Aktuelle Debian auf einem physikalischen Host.
  9. Ich w?rde es begr?ssen, wenn ich hier weitere Hinweise kriege. Danke.
  10. Thank you, looks already more interesting. For using Froxlor over SSL, I should make the same if-statement in the IP:Port section > Own vHost Settings?
  11. Ja, alleine der Speicher (ab 2GB) ist begrenzt und auf keinen Fall aufgebraucht. Alles andere ist uneingeschr?nkt.
  12. It's delayed for three years and lost its priority as its target version. I'll look for my own solution because unfortunately I don't find time to make a patch which will be useful. Thanks. ;-)
  13. I have another idea: In Settings > SSL Settings > as I understand it the path values are directly written into the vhost configuration, is that correct? In case, using the ${HTTP_HOST} apache variable should work in my point of view. For example: cert file path could be "/etc/apache2/ssl/${HTTP_HOST}.crt" which should be read correctly by the httpd daemon? Of course, this always requires that the HTTP_HOST is matching with the request of Froxlor and customers' webs...
  14. The other ticket with the same request is around three years old with 0.9.23 as previous target version.... As a lot of feature requests have been done, why such an important feature has to wait that much time? I know this is a free open source project but I was just surprised in a bad way that this ticket seems to have no priority at all...