šŸ”“ January 2024 Alert: Forum support inactive!
New forum registration are currently closed.
Use GitHub discussions
.

    UVdesk

    • Login
    • Search
    • Recent

    Solved Impossible to install, stall at step 1 on php8, step 4 on php7.3

    Bug Report
    4
    16
    10900
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Komal Sharma
      Komal Sharma UVdesk Staff mod last edited by

      @gacabinetco

      The latest version of "doctrine/doctrine-fixtures-bundle" is not compatible with uvdesk.

      You can be fixed this issue by changing the version in composer.json in uvdesk:

      "doctrine/doctrine-fixtures-bundle": "^3.4",
       **TO**
      "doctrine/doctrine-fixtures-bundle": "3.4.1",
      

      After Updating the changes in composer.json
      Finally, run the below command in your project root directory:
      composer update and setup again.

      Follow this link for the issue in step 4 from here.

      I Hope, This will resolve your issue. If you have still facing the error let us know.

      G 1 Reply Last reply Reply Quote 0
      • G
        ghislain @Komal Sharma last edited by ghislain

        @komal-sharma
        hi,

        what i have done:

        8484 [26/07/22 08:28:05] rm -Rf helpdesk-project/
        8485 [26/07/22 08:28:16] sudo -u support2022 composer create-project uvdesk/community-skeleton helpdesk-project
        8486 [26/07/22 08:28:53] cd helpdesk-project/
        8487 [26/07/22 08:28:56] nano composer.json => Done the change requested
        8488 [26/07/22 08:29:12] sudo -u support2022 composer update

        Loading composer repositories with package information
        Restricting packages listed in "symfony/symfony" to "^5.4"
        Updating dependencies
        Lock file operations: 0 installs, 2 updates, 0 removals
          - Downgrading doctrine/doctrine-fixtures-bundle (3.4.2 => 3.4.1)
          - Downgrading doctrine/persistence (3.0.2 => 2.5.3)
        Writing lock file
        Installing dependencies from lock file (including require-dev)
        Package operations: 0 installs, 2 updates, 0 removals
          - Downgrading doctrine/persistence (3.0.2 => 2.5.3): Extracting archive
          - Downgrading doctrine/doctrine-fixtures-bundle (3.4.2 => 3.4.1): Extracting archive
        Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
        Package symfony/swiftmailer-bundle is abandoned, you should avoid using it. Use symfony/mailer instead.
        Generating optimized autoload files
        composer/package-versions-deprecated: Generating version class...
        composer/package-versions-deprecated: ...done generating version class
        117 packages you are using are looking for funding.
        Use the `composer fund` command to find out more!
        
        What about running composer global require symfony/thanks && composer thanks now?
        This will spread some šŸ’–  by sending a ā˜…  to the GitHub repositories of your fellow package maintainers.
        
        Run composer recipes at any time to see the status of your Symfony recipes.
        
        Executing script cache:clear [OK]
        Executing script assets:install public [OK]
        

        8489 [26/07/22 08:29:37] sudo -u support2022 php bin/console c:c

         // Clearing the cache for the dev environment with debug true                                                          
        
                                                                                                                                
         [OK] Cache for the "dev" environment (debug=true) was successfully cleared.                                            
                                                                                         
        

        but now it fails at step 2 Something went wrong ! Please try again

        complete trace at https://support2020.aqueos.net/uvdesk/public/_profiler/262892

        CRITICAL 08:36:10 	request 	Uncaught PHP Exception Twig\Error\RuntimeError: "An exception has been thrown during the rendering of a template ("Environment variable not found: "APP_SECRET".")." at /home/support2020/public_html/uvdesk/vendor/symfony/web-profiler-bundle/Resources/views/Collector/exception.html.twig line 6
        
        {
            "exception": {}
        }
        

        --
        cordialement,
        Ghislain

        1 Reply Last reply Reply Quote 0
        • Komal Sharma
          Komal Sharma UVdesk Staff mod last edited by

          @ghislain
          Follow this blog for installation from here.

          Let us know which PHP version you are using.

          Please check once the below steps before setup and make changes accordingly:

          • The web server might don't have permission to allow overriding of the Apache config on a per-directory basis. Allow Override needs to be set to All for the directory block as mentioned below:
          **<Directory /home/users/var/www/htdocs>
          Options Indexes FollowSymLinks
          AllowOverride All
          Require all granted**
          
          • If your database password contains some special character(such as #$%@) then change your password and make it without a special character.

          • Locate the .env file in your project and make sure APP_ENV=dev when you are doing your setup.

          • Allow read-write permission for the below file & folder:

          For .env file – chmod 775 -R path of .env file of UVdesk project

          For var folder -chmod 775 -R path of var folder of UVdesk project

          For config folder – chmod 775 -R path of config folder of UVdesk project

          • And also check the max execution time if it is 30sec then increase it. check here

          Also check this for your reference: #161

          Restart your server.
          And clear your project cache by:
          php bin/console c:c

          Now try to install your project.

          1 Reply Last reply Reply Quote 0
          • G
            ghislain last edited by

            thanks, it works on php8.0 with the composer modification but this all feel quite brittle, installation is problematic and the framework and install scream a lot of deprecation error.

            thanks for the help.

            best regards,
            Ghislain.

            1 Reply Last reply Reply Quote 0
            • Topic has been marked as solved  peopleinside peopleinside 
            • C
              compay last edited by

              Hello, I'm the same

              but in my case it stops at step 2

              I have already done several things, but I have run out of tricks and I don't know what to do.

              1870d2a5-0e24-47fd-ad4f-f0354c2365b0-image.png

              1 Reply Last reply Reply Quote 0
              • C
                compay last edited by

                df204344-0080-4d59-9253-7c97012427e2-image.png

                1 Reply Last reply Reply Quote 0
                • Komal Sharma
                  Komal Sharma UVdesk Staff mod last edited by

                  @compay

                  It can be because of these reasons.
                  Check the below these cases and make changes accordingly:

                  1. A web server might don't have permission to allow overriding of the Apache config on a per-directory basis. Allow Override needs to be set to All for the directory block as mentioned below:
                  <Directory /home/users/var/www/htdocs>
                  Options Indexes FollowSymLinks
                  AllowOverride All
                  Require all granted
                  
                  1. If your database password contains some special character(such as #$%@) then change your password and make it without special characters.

                  2. Locate the .env file in your project and make sure APP_ENV=dev when you are doing your setup.

                  3. Allow read-write permission for the below file & folder:

                  • For .env file – chmod 777 -R path of .env file of UVdesk project
                  • For Var folder -chmod 777 -R path of var folder of UVdesk project
                  • For Config folder – chmod 777 -R path of config folder of UVdesk
                  • For Public folder – chmod 777 -R path of the public folder of UVdesk
                  • For Migration folder – chmod 777 -R path of the migration folder of UVdesk
                  1. It happens mainly because of less execution time in the php.ini file.
                    By default, max_execution_time is 30 sec you need to increase it and restart your server.
                    Check here how to increase the max-execution time.
                    Restart your server.

                  And clear your project cache by:
                  php bin/console c:c
                  Now try to install your project.

                  => Once you try with the manual installation of uvdesk from here.

                  If the issue is still in the manual installation setup, let us know.

                  1 Reply Last reply Reply Quote 0
                  • C
                    compay last edited by

                    Hello, thank you for your instructions, I was able to install them thanks to your tutorial, but the problem is that I cannot enter the admin and it does not allow me to attach an image when I try to send as a user.

                    I don't know how to remove the production tools that appear at the bottom of the page, I never worked with Laravel.

                    But if you explain to me what I have to do once I have it installed, I do it.

                    63d853c8-1357-4213-b019-12b30b569726-image.png

                    1 Reply Last reply Reply Quote 0
                    • C
                      compay last edited by

                      I have already removed the tools now it has gone from local to production, but I can't enter the admin I still don't know why.

                      This is my configuration, I still don't know if I need more permissions to upload files

                      bc693d26-1729-400f-b1a8-a3ff91fd1e43-image.png

                      1 Reply Last reply Reply Quote 0
                      • C
                        compay last edited by

                        This is what happens if I try to upload an image from the side of the user asking for support

                        3971ca40-d62e-4aef-91dc-c759f77cccf0-image.png

                        peopleinside 2 Replies Last reply Reply Quote 0
                        • Referenced by  peopleinside peopleinside 
                        • Topic has been marked as unsolved  peopleinside peopleinside 
                        • peopleinside
                          peopleinside EX helping member @compay last edited by

                          @compay thank you for your update, let's wait a staff reply from UVdesk šŸ™‚

                          šŸ’¬ You can also ask help on GitHub Discussions
                          šŸ”“ I am no more active on Uvdesk
                          šŸ”“ Forum support is inactive!

                          1 Reply Last reply Reply Quote 0
                          • peopleinside
                            peopleinside EX helping member @compay last edited by

                            I'm sorry to see no reply from UVdesk.
                            @Komal-Sharma

                            šŸ’¬ You can also ask help on GitHub Discussions
                            šŸ”“ I am no more active on Uvdesk
                            šŸ”“ Forum support is inactive!

                            peopleinside 1 Reply Last reply Reply Quote 0
                            • Topic has been marked as solved  peopleinside peopleinside 
                            • peopleinside
                              peopleinside EX helping member @peopleinside last edited by

                              I'm marking this topic as solved as the topic has been started from the author that has received the reply.

                              šŸ’¬ You can also ask help on GitHub Discussions
                              šŸ”“ I am no more active on Uvdesk
                              šŸ”“ Forum support is inactive!

                              1 Reply Last reply Reply Quote 0
                              • Komal Sharma
                                Komal Sharma UVdesk Staff mod last edited by Komal Sharma

                                @compay

                                Your issue is due to insufficient directory permissions. To resolve this, change the owner of the directory accordingly:

                                1. First, you will directory user ownership to a specific non-root user using this command:

                                  $ chown -R {user_name}:{user_group} {target_directory}

                                  Ex: $ chown -R uvdesk:uvdesk community-skeleton

                                2. Second, add this user to the www-data apache user group using the following command:

                                  Add user to www-data group:

                                  $ usermod -aG {user} www-data;

                                  Ex: $ usermod -aG uvdesk www-data;

                                  Verify that the user has been added to the www-data group:

                                  $ groups <your-user-name>;

                                  Ex: $ groups uvdesk;

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post