weird issues, htaccess without effect, wget not working, fcgi errors

Discussion in 'General' started by manarak, Nov 22, 2023.

  1. manarak

    manarak Member

    I installed a server with Ubuntu LTS using a perfect server guide from this site.
    I run a phpBB on it.

    All runs normally, until today I tried to modify its htaccess file to gain direct access to a subdirectory where my AWstats live, but to no avail. Instead a rabbit hole opened up.

    I tried various variations, among which
    Code:
    RewriteCond %{REQUEST_URI} ^/stats/
    RewriteRule ^(.*)$ /stats/index.php [QSA,L]
    
    RewriteCond %{REQUEST_URI} !^/stats
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ app.php [QSA,L]
    
    but all gets routed to symphony anyway and a route not found error is displayed.

    so I started checking configurations, apache directives, etc. AllowOverride All is enabled, all seems normal.

    the website runs (fine) on PHP-FPM, so I tried to switch to fastFCGI and error 500 appears. weird.

    I try to check different things, but I have no clue what is wrong.

    I tried to run Till's test script as described, but the command only produced an empty file, so I downloaded it manually and ran it.

    results and logs attached
     

    Attached Files:

  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Which guide?

    Adding
    Code:
    Alias "/stats" "{DOCROOT_CLIENT}/stats"
    should work for you.
     
  3. manarak

    manarak Member

  4. manarak

    manarak Member

    any idea why fastFCGI doen't work though ?
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The date of a guide does not matter, the only thing that matters is which operating system version it is for and the one guide you mentioned is for Ubuntu 18.04 only and the other guide is for Ubuntu 20.04 only. So ou hopefully have chosen the guide that matched the operating system of your server.
     
  6. manarak

    manarak Member

    yes, so much is certain!

    any idea why fastCGI doesn't work ?
     
    Last edited: Nov 22, 2023
  7. manarak

    manarak Member

    I put that in the Apache Directives in the "options" tab for the domain, but sadly, that didn't do the trick.
     
  8. manarak

    manarak Member

    what could I do to fix the issues ?
     
  9. SamTzu

    SamTzu Active Member

    Some Symphony / Laravel code simply does not work well with fastCGI.
    There is still lots of code that won't work with anything above PHP 7.3.
    There are good quides here how to install additional PHP versions for ISPConfig.
    I always install PHP 7.3 just in case...
    https://www.howtoforge.com/ispconfig-php-ubuntu

    Try to reset file permissions for cache and / or use older PHP version.
    sudo chmod -R o+w var/cache/
     
    Last edited: Nov 23, 2023
  10. SamTzu

    SamTzu Active Member

    You can also use terminal and try composer update on the /web directory but remember to take backup first.
    It should give you something like this:
    Code:
    root@sami:/var/www/dev.mattila.eu/web# composer update
    Do not run Composer as root/super user! See https://getcomposer.org/root for details
    Continue as root/super user [yes]? yes
    Loading composer repositories with package information
    Updating dependencies
    Lock file operations: 0 installs, 15 updates, 0 removals
      - Upgrading filp/whoops (2.15.3 => 2.15.4)
      - Upgrading graham-campbell/result-type (v1.1.1 => v1.1.2)
      - Upgrading laravel/serializable-closure (v1.3.2 => v1.3.3)
      - Upgrading phpoption/phpoption (1.9.1 => 1.9.2)
      - Upgrading ramsey/uuid (4.7.4 => 4.7.5)
      - Upgrading symfony/console (v5.4.28 => v5.4.31)
      - Upgrading symfony/deprecation-contracts (v3.3.0 => v3.4.0)
      - Upgrading symfony/event-dispatcher-contracts (v3.3.0 => v3.4.0)
      - Upgrading symfony/http-foundation (v5.4.30 => v5.4.31)
      - Upgrading symfony/http-kernel (v5.4.30 => v5.4.31)
      - Upgrading symfony/string (v6.3.5 => v6.3.8)
      - Upgrading symfony/translation-contracts (v3.3.0 => v3.4.0)
      - Upgrading symfony/yaml (v6.3.7 => v6.3.8)
      - Upgrading theseer/tokenizer (1.2.1 => 1.2.2)
      - Upgrading vlucas/phpdotenv (v5.5.0 => v5.6.0)
    Writing lock file
    Installing dependencies from lock file (including require-dev)
    Package operations: 0 installs, 15 updates, 0 removals
      - Downloading symfony/string (v6.3.8)
      - Downloading symfony/console (v5.4.31)
      - Downloading phpoption/phpoption (1.9.2)
      - Downloading graham-campbell/result-type (v1.1.2)
      - Downloading vlucas/phpdotenv (v5.6.0)
      - Downloading symfony/http-foundation (v5.4.31)
      - Downloading symfony/http-kernel (v5.4.31)
      - Downloading ramsey/uuid (4.7.5)
      - Downloading symfony/translation-contracts (v3.4.0)
      - Downloading laravel/serializable-closure (v1.3.3)
      - Downloading symfony/yaml (v6.3.8)
      - Downloading filp/whoops (2.15.4)
      - Downloading theseer/tokenizer (1.2.2)
      - Upgrading symfony/string (v6.3.5 => v6.3.8): Extracting archive
      - Upgrading symfony/deprecation-contracts (v3.3.0 => v3.4.0): Extracting archive
      - Upgrading symfony/console (v5.4.28 => v5.4.31): Extracting archive
      - Upgrading phpoption/phpoption (1.9.1 => 1.9.2): Extracting archive
      - Upgrading graham-campbell/result-type (v1.1.1 => v1.1.2): Extracting archive
      - Upgrading vlucas/phpdotenv (v5.5.0 => v5.6.0): Extracting archive
      - Upgrading symfony/http-foundation (v5.4.30 => v5.4.31): Extracting archive
      - Upgrading symfony/event-dispatcher-contracts (v3.3.0 => v3.4.0): Extracting archive
      - Upgrading symfony/http-kernel (v5.4.30 => v5.4.31): Extracting archive
      - Upgrading ramsey/uuid (4.7.4 => 4.7.5): Extracting archive
      - Upgrading symfony/translation-contracts (v3.3.0 => v3.4.0): Extracting archive
      - Upgrading laravel/serializable-closure (v1.3.2 => v1.3.3): Extracting archive
      - Upgrading symfony/yaml (v6.3.7 => v6.3.8): Extracting archive
      - Upgrading filp/whoops (2.15.3 => 2.15.4): Extracting archive
      - Upgrading theseer/tokenizer (1.2.1 => 1.2.2): Extracting archive
    Package fruitcake/laravel-cors is abandoned, you should avoid using it. No replacement was suggested.
    Package gdm/ispconfig-soap-client is abandoned, you should avoid using it. No replacement was suggested.
    Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
    Generating optimized autoload files
    > Illuminate\Foundation\ComposerScripts::postAutoloadDump
    > @php artisan package:discover --ansi
    Discovered Package: facade/ignition
    Discovered Package: fruitcake/laravel-cors
    Discovered Package: laravel/cashier
    Discovered Package: laravel/sail
    Discovered Package: laravel/sanctum
    Discovered Package: laravel/tinker
    Discovered Package: livewire/livewire
    Discovered Package: nesbot/carbon
    Discovered Package: nunomaduro/collision
    Package manifest generated successfully.
    79 packages you are using are looking for funding.
    Use the `composer fund` command to find out more!
    > @php artisan vendor:publish --tag=laravel-assets --ansi --force
    No publishable resources for tag [laravel-assets].
    Publishing complete.
    No security vulnerability advisories found
    root@sami:/var/www/dev.mattila.eu/web# 
     
  11. manarak

    manarak Member

    Thank you SamTzu for these insights.
    So FCGI might not have a problem after all.

    What about the .htaccess issue ?

    I'm familiar with composer, I use it for my Drupal sites - just upgraded to Drupal 10.1.6 with 90 modules... success after 3 hours of tinkering with dev and beta versions, patches! yay :)
     
    SamTzu likes this.

Share This Page