Bagisto Forum

    Bagisto

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    admin/login not found. Known solutions won't work.

    Installing Bagisto
    2
    9
    1943
    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.
    • B
      Balthazar last edited by

      So I'm having the problem that every route works but not admin login.
      And I've checked this: https://forums.bagisto.com/topic/77/admin-login-route-not-found

      But there are a couple of problems:
      The only thing I can do from this list is restart the server via a panel and ofc php artisan commands.
      I can neither read nor edit files in /etc/apache2
      Then I don't know if this is translatable to .htaccess

      all files reside in http://myserver.com/public but I can't move and link them to public_html because of missing permissions.

      My provider (cloudways) has an outdated guide for version <0.2 which won't work.

      And most importantly all the posts asking this question in this forum link to that one from 2019 but it does not help me as pointed out.

      1 Reply Last reply Reply Quote 0
      • devansh-webkul
        devansh-webkul last edited by devansh-webkul

        You just need to map your domain to public. For e.g. let say you have the below scenario,

        https://example.com -----> public_html

        First case

        Then you can do one thing just install Bagisto separately and the symlink the bagisto-project/public folder to public_html.

        Second case

        Install your Bagisto and map the domain to bagisto-project/public folder.

        NOTE: Make sure your bagisto installed properly and you have published all your packages.

        1 Reply Last reply Reply Quote 0
        • B
          Balthazar last edited by Balthazar

          Hm... I pointed the test domain to public_html/public/ but the error persists.
          Do I need to run some command after updating the paths in .env ?

          1 Reply Last reply Reply Quote 0
          • devansh-webkul
            devansh-webkul last edited by

            Nothing just place all your Laravel folders file in public_html folder.

            1 Reply Last reply Reply Quote 0
            • B
              Balthazar last edited by Balthazar

              OK. I have these files in public_html:

              drwxrwxr-x   6 1009   33   4096 Sep 27 13:11 app
              -rwxrwxr-x   1 1009   33   1686 Sep 27 13:11 artisan
              drwxrwxr-x   2 1009   33   4096 Sep 27 13:11 bin
              drwxrwxr-x   3 1009   33   4096 Sep 27 13:11 bootstrap
              -rwxrwxr-x   1 1009   33    358 Sep 27 13:11 bower.json
              -rwxrwxr-x   1 1009   33  42865 Sep 27 13:11 CHANGELOG for v0.1.x.md
              -rw-rw-r--   1 1009   33    926 Sep 27 13:11 CHANGELOG for v0.2.x.md
              -rw-rw-r--   1 1009   33  75124 Sep 27 13:11 CHANGELOG for v1.x.x.md
              -rw-rw-r--   1 1009   33    211 Sep 27 13:11 codeception.yml
              -rw-rw-r--   1 1009   33   3351 Sep 27 13:11 CODE_OF_CONDUCT.md
              -rwxrwxr-x   1 1009   33   6418 Sep 27 13:11 composer.json
              -rw-rw-r--   1 1009   33 425203 Sep 27 13:11 composer.lock
              drwxrwxr-x   2 1009   33   4096 Oct 11 09:57 config
              -rw-rw-r--   1 1009   33   2915 Sep 27 13:11 CONTRIBUTING.md
              drwxrwxr-x   5 1009   33   4096 Sep 27 13:11 database
              -rw-rw-r--   1 1009   33    255 Sep 27 13:11 .editorconfig
              -rw-rw-r--   1 1009   33   1582 Oct 13 05:05 .env
              -rw-rw-r--   1 1009   33   1431 Sep 27 13:11 .env.example
              -rw-rw-r--   1 1009   33    807 Sep 27 13:11 .env.testing
              -rw-rw-r--   1 1009   33    111 Sep 27 13:11 .gitattributes
              drwxrwxr-x   4 1009   33   4096 Sep 27 13:11 .github
              -rw-rw-r--   1 1009   33    349 Sep 27 13:11 .gitignore
              -rw-rw-r--   1 1009   33   1078 Sep 27 13:11 LICENSE
              -rwxrwxr-x   1 1009   33    971 Sep 27 13:11 migration guide.md
              -rwxrwxr-x   1 1009   33   1234 Sep 27 13:11 package.json
              drwxrwxr-x   3 1009   33   4096 Sep 27 13:11 packages
              -rwxrwxr-x   1 1009   33   1134 Sep 27 13:11 phpunit.xml
              drwxrwxr-x   4 1009   33   4096 Oct 11 09:57 public
              -rwxrwxr-x   1 1009   33   6435 Sep 27 13:11 README.md
              drwxrwxr-x   6 1009   33   4096 Sep 27 13:11 resources
              drwxrwxr-x   2 1009   33   4096 Sep 27 13:11 routes
              -rwxrwxr-x   1 1009   33    563 Sep 27 13:11 server.php
              drwxrwxr-x   7 1009   33   4096 Sep 27 13:11 storage
              drwxrwxr-x   2 1009   33   4096 Oct 11 09:57 stubs
              drwxrwxr-x   9 1009   33   4096 Sep 27 13:11 tests
              drwxrwxr-x  74 1009   33   4096 Oct 11 09:55 vendor
              -rwxrwxr-x   1 1009   33    549 Sep 27 13:11 webpack.mix.js
              
              

              and the domain points to /public_html/public/
              Everything else seems to work but the admin login route does not.

              1 Reply Last reply Reply Quote 0
              • devansh-webkul
                devansh-webkul last edited by

                Hi,

                Just publish your packages.

                php artisan vendor:publish --all --force and then php artisan optimize.

                1 Reply Last reply Reply Quote 0
                • B
                  Balthazar last edited by

                  I did that but the result is the same. 😞

                  1 Reply Last reply Reply Quote 0
                  • devansh-webkul
                    devansh-webkul last edited by

                    Just check, if in .env admin URL changed or not.

                    1 Reply Last reply Reply Quote 0
                    • B
                      Balthazar last edited by Balthazar

                      I did a couple of tests. Before I had the URL for the admin page entered and reviewing the .env.testing and .env.example I changed it to the path / route without URL domain and protocol. That did the trick. Thank you.

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