Jump to content
Froxlor Forum

d00p

Administrators
  • Posts

    10302
  • Joined

  • Last visited

  • Days Won

    43

Posts posted by d00p

  1. 37 minutes ago, dyers said:

    I also checked the database for the local froxlor user. User with adminid 1 seems to have been renamed in the past to a custom login name. But that shouldn't be an issue, should it

    No nothing user related has been renamed. The local user for php-fpm has nothing to do with any user within froxlor itself

    38 minutes ago, dyers said:

    which came back as '2y'

    2 should be blowfish, correct?

    Yes

    38 minutes ago, dyers said:

    How can I match - or regenerate a new password for the user? Although I am certain that it still worked before and after the upgrade to 20.04, where I logged in to froxlor for a quick sanity check.

    User-Login should work without any issues after a update. Never had any issues with that.

    10 minutes ago, dyers said:

    I am one step further. mysql is throwing errors for a denied user.

    A deprecated warning will not prevent any logins

    Also MySQL User Login != Froxlor webui Login. These are completely different things.

     

    As said before, mostly this is something related to sessions. Please check Webserver and php-fpm logs.

  2. 12 minutes ago, dyers said:

    ibnss-mysql-bg

    This still exists? It should be libnss-extrausers for years now.

    13 minutes ago, dyers said:

    fixed location in froxlor vhosts, apparently moved from /var/www/froxlor to /var/www/html/froxlor

    Is mentioned in the announcement of 2.0

    Regarding login, validate the froxlor local user and the permissions on /car/customers/tmp/froxlor.panel/ - although there should definitely be something in the Webserver errorlog or php-fpm log

  3. Die config für froxlor sollte so aussehen, musste evtl schauen ob da deine customizations irgendwo nen strich durch die rechnung machen
     

    allow_call_time_pass_reference = Off
    allow_url_fopen = On
    asp_tags = Off
    disable_classes =
    disable_functions = curl_multi_exec,exec,parse_ini_file,passthru,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,shell_exec,show_source,system
    display_errors = Off
    display_startup_errors = Off
    enable_dl = Off
    error_reporting = E_ALL & ~E_NOTICE
    expose_php = Off
    file_uploads = On
    cgi.force_redirect = 1
    gpc_order = "GPC"
    html_errors = Off
    ignore_repeated_errors = Off
    ignore_repeated_source = Off
    include_path = ".:{PEAR_DIR}"
    log_errors = On
    log_errors_max_len = 1024
    magic_quotes_gpc = Off
    magic_quotes_runtime = Off
    magic_quotes_sybase = Off
    max_execution_time = 60
    max_input_time = 60
    memory_limit = 16M
    noutput_buffering = 4096
    post_max_size = 16M
    precision = 14
    register_argc_argv = Off
    register_globals = Off
    report_memleaks = On
    sendmail_path = "/usr/sbin/sendmail -t -i -f {CUSTOMER_EMAIL}"
    session.auto_start = 0
    session.bug_compat_42 = 0
    session.bug_compat_warn = 1
    session.cache_expire = 180
    session.cache_limiter = nocache
    session.cookie_domain =
    session.cookie_lifetime = 0
    session.cookie_path = /
    session.entropy_file = /dev/urandom
    session.entropy_length = 16
    session.gc_divisor = 1000
    session.gc_maxlifetime = 1440
    session.gc_probability = 1
    session.name = PHPSESSID
    session.referer_check =
    session.save_handler = files
    session.save_path = "{TMP_DIR}"
    session.serialize_handler = php
    session.use_cookies = 1
    session.use_trans_sid = 0
    short_open_tag = On
    suhosin.mail.protect = 1
    suhosin.simulation = Off
    track_errors = Off
    upload_max_filesize = 32M
    upload_tmp_dir = "{TMP_DIR}"
    variables_order = "GPCS"
    ;mail.add_x_header = On
    ;mail.log = "/var/log/phpmail.log"
    opcache.restrict_api = ""

     

  4. Wenn das ein debian ist und du das via apt installiert hast sind die sachen vermutlich nur via alias verfügbar, je nachdem wie das paket das macht. Das kann funktionieren, aber bei einem standard froxlor setup mit php-fpm z.B. wird das so nicht funktionieren (berechtigungen u.A.).

    Entweder manuell installieren, z.B. für einen dafür angelegten Kunden mit eigener (Sub-)domain oder in /var/www/html/froxlor packen und via froxlor domain drauf zugreifen. 

    "Kompliziertere" Variante wär dann die config des Aliases (sofern vorhanden, kenne jetzt die zwei pakete nicht adhoc) entsprechend z.B. mit dem php-fpm socket von froxlor zu bestücken und berechtigungen anzupassen, ist aber dann ggfls nich update-sicher

  5. Löst die domain denn korrekt auf die im vhost gezeigten IP adressen auf? Es hat sich nix "bahnbrechendes" geändert wie der webserver funktioniert...

    4 minutes ago, Pagefreak said:

    Wenn ich die Seite nun jedoch aufrufe, werde ich auf eine gänzlich andere Subdomain geleitet

    Na wirst du wirklich UMGELEITET (http redirect) oder landet die domain in einem anderen docroot? großer unterschied

×
×
  • Create New...