Where does php+laravel reads db connection string because runtime defaulting to user id not defined anywhere...












0















I am hosting my php+laravel rest API application in azure app service (windows). The app server comes with 'mysql in app' (build into it). I am able access the mysql database through myphpadmin. I can see there were two predefined users, one is root and another one is azure. To connect to database using myphpadmin, it uses azure user id.



In my application in .env I have DB_USERNAME set to azure and in database.php, if the user id is not found in config default it is set to default to 'azure'. Also in azure app server's app setting I have all the connection strings defined and there as well, I am using azure as the DB_USERNAME.



But when I ran postman to one of the end point, I noticed, the end point is failing because of "Access denied for user 'root'@'localhost'". I am really confused where would my application uses root as the username instead of azure.



Thanks










share|improve this question



























    0















    I am hosting my php+laravel rest API application in azure app service (windows). The app server comes with 'mysql in app' (build into it). I am able access the mysql database through myphpadmin. I can see there were two predefined users, one is root and another one is azure. To connect to database using myphpadmin, it uses azure user id.



    In my application in .env I have DB_USERNAME set to azure and in database.php, if the user id is not found in config default it is set to default to 'azure'. Also in azure app server's app setting I have all the connection strings defined and there as well, I am using azure as the DB_USERNAME.



    But when I ran postman to one of the end point, I noticed, the end point is failing because of "Access denied for user 'root'@'localhost'". I am really confused where would my application uses root as the username instead of azure.



    Thanks










    share|improve this question

























      0












      0








      0








      I am hosting my php+laravel rest API application in azure app service (windows). The app server comes with 'mysql in app' (build into it). I am able access the mysql database through myphpadmin. I can see there were two predefined users, one is root and another one is azure. To connect to database using myphpadmin, it uses azure user id.



      In my application in .env I have DB_USERNAME set to azure and in database.php, if the user id is not found in config default it is set to default to 'azure'. Also in azure app server's app setting I have all the connection strings defined and there as well, I am using azure as the DB_USERNAME.



      But when I ran postman to one of the end point, I noticed, the end point is failing because of "Access denied for user 'root'@'localhost'". I am really confused where would my application uses root as the username instead of azure.



      Thanks










      share|improve this question














      I am hosting my php+laravel rest API application in azure app service (windows). The app server comes with 'mysql in app' (build into it). I am able access the mysql database through myphpadmin. I can see there were two predefined users, one is root and another one is azure. To connect to database using myphpadmin, it uses azure user id.



      In my application in .env I have DB_USERNAME set to azure and in database.php, if the user id is not found in config default it is set to default to 'azure'. Also in azure app server's app setting I have all the connection strings defined and there as well, I am using azure as the DB_USERNAME.



      But when I ran postman to one of the end point, I noticed, the end point is failing because of "Access denied for user 'root'@'localhost'". I am really confused where would my application uses root as the username instead of azure.



      Thanks







      php laravel azure






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 5:06









      unniunni

      84




      84
























          2 Answers
          2






          active

          oldest

          votes


















          1














          Remember to run php artisan config:cache command when you change any data in env



          laravel always read config data from its cache.



          so if your .env credentials are changed in server you also have to cache again that credentials



          also make sure that your database config file reading all the credentials from .env by default.



          Example:



          'mysql' => array(
          'driver' => 'mysql',
          'host' => env('DB_HOST','localhost'),
          'database' => env('DB_DATABASE','billing'),
          'username' => env('DB_USERNAME','root'),
          'password' => env('DB_PASSWORD', '1234'),
          'charset' => 'utf8',
          'collation' => 'utf8_unicode_ci',
          'prefix' => '',
          )


          Note:




          If you execute the config:cache command during your deployment
          process, you should be sure that you are only calling the env function
          from within your configuration files. Once the configuration has been
          cached, the .env file will not be loaded and all calls to the env
          function will return null.







          share|improve this answer



















          • 2





            php artisan config:cache did the trick, thanks

            – unni
            Nov 21 '18 at 5:38



















          0














          You also need to configure it not just in .env as @EmtiazZahid has suggested to you, and you must restart your server each time you do any configuration in .env






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53405563%2fwhere-does-phplaravel-reads-db-connection-string-because-runtime-defaulting-to%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Remember to run php artisan config:cache command when you change any data in env



            laravel always read config data from its cache.



            so if your .env credentials are changed in server you also have to cache again that credentials



            also make sure that your database config file reading all the credentials from .env by default.



            Example:



            'mysql' => array(
            'driver' => 'mysql',
            'host' => env('DB_HOST','localhost'),
            'database' => env('DB_DATABASE','billing'),
            'username' => env('DB_USERNAME','root'),
            'password' => env('DB_PASSWORD', '1234'),
            'charset' => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix' => '',
            )


            Note:




            If you execute the config:cache command during your deployment
            process, you should be sure that you are only calling the env function
            from within your configuration files. Once the configuration has been
            cached, the .env file will not be loaded and all calls to the env
            function will return null.







            share|improve this answer



















            • 2





              php artisan config:cache did the trick, thanks

              – unni
              Nov 21 '18 at 5:38
















            1














            Remember to run php artisan config:cache command when you change any data in env



            laravel always read config data from its cache.



            so if your .env credentials are changed in server you also have to cache again that credentials



            also make sure that your database config file reading all the credentials from .env by default.



            Example:



            'mysql' => array(
            'driver' => 'mysql',
            'host' => env('DB_HOST','localhost'),
            'database' => env('DB_DATABASE','billing'),
            'username' => env('DB_USERNAME','root'),
            'password' => env('DB_PASSWORD', '1234'),
            'charset' => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix' => '',
            )


            Note:




            If you execute the config:cache command during your deployment
            process, you should be sure that you are only calling the env function
            from within your configuration files. Once the configuration has been
            cached, the .env file will not be loaded and all calls to the env
            function will return null.







            share|improve this answer



















            • 2





              php artisan config:cache did the trick, thanks

              – unni
              Nov 21 '18 at 5:38














            1












            1








            1







            Remember to run php artisan config:cache command when you change any data in env



            laravel always read config data from its cache.



            so if your .env credentials are changed in server you also have to cache again that credentials



            also make sure that your database config file reading all the credentials from .env by default.



            Example:



            'mysql' => array(
            'driver' => 'mysql',
            'host' => env('DB_HOST','localhost'),
            'database' => env('DB_DATABASE','billing'),
            'username' => env('DB_USERNAME','root'),
            'password' => env('DB_PASSWORD', '1234'),
            'charset' => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix' => '',
            )


            Note:




            If you execute the config:cache command during your deployment
            process, you should be sure that you are only calling the env function
            from within your configuration files. Once the configuration has been
            cached, the .env file will not be loaded and all calls to the env
            function will return null.







            share|improve this answer













            Remember to run php artisan config:cache command when you change any data in env



            laravel always read config data from its cache.



            so if your .env credentials are changed in server you also have to cache again that credentials



            also make sure that your database config file reading all the credentials from .env by default.



            Example:



            'mysql' => array(
            'driver' => 'mysql',
            'host' => env('DB_HOST','localhost'),
            'database' => env('DB_DATABASE','billing'),
            'username' => env('DB_USERNAME','root'),
            'password' => env('DB_PASSWORD', '1234'),
            'charset' => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix' => '',
            )


            Note:




            If you execute the config:cache command during your deployment
            process, you should be sure that you are only calling the env function
            from within your configuration files. Once the configuration has been
            cached, the .env file will not be loaded and all calls to the env
            function will return null.








            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 21 '18 at 5:27









            Emtiaz ZahidEmtiaz Zahid

            1,043616




            1,043616








            • 2





              php artisan config:cache did the trick, thanks

              – unni
              Nov 21 '18 at 5:38














            • 2





              php artisan config:cache did the trick, thanks

              – unni
              Nov 21 '18 at 5:38








            2




            2





            php artisan config:cache did the trick, thanks

            – unni
            Nov 21 '18 at 5:38





            php artisan config:cache did the trick, thanks

            – unni
            Nov 21 '18 at 5:38













            0














            You also need to configure it not just in .env as @EmtiazZahid has suggested to you, and you must restart your server each time you do any configuration in .env






            share|improve this answer




























              0














              You also need to configure it not just in .env as @EmtiazZahid has suggested to you, and you must restart your server each time you do any configuration in .env






              share|improve this answer


























                0












                0








                0







                You also need to configure it not just in .env as @EmtiazZahid has suggested to you, and you must restart your server each time you do any configuration in .env






                share|improve this answer













                You also need to configure it not just in .env as @EmtiazZahid has suggested to you, and you must restart your server each time you do any configuration in .env







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 '18 at 5:39









                Akhtar MunirAkhtar Munir

                6611




                6611






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53405563%2fwhere-does-phplaravel-reads-db-connection-string-because-runtime-defaulting-to%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith