Hi …I had installed Invoice Ninja in shared hosting using Softaculous …initially, it wasn’t working …after creating a subdomain and corrected the index file by studying Laravel installation, finally, i m able to get the log-in page…but when I give the email ID and password set on DB as user,i m not able to log in …based on one forum I m also tried below steps Run php artisan tinker in the root folder of the app and then bcrypt('new password');
still, i m not able to log in
i m getting error as 401: These credentials do not match our records
The fields i have on login page are
Email - Given the email ID in the user table of DB
Password - Given the password reset using php artisan tinkerin the root folder of the app and thenbcrypt(‘new password’);
OTP (Optional)
Secret(Optional)
while checking Laravel log all I m getting the below error…since I m new here not sure what to do.
[2021-04-13 17:18:15] production.INFO: Illuminate\Support\MessageBag Object
(
[messages:protected] => Array
(
[password] => Array
(
[0] => The password field is required.
)
Can you explain what you mean by “corrected the index file by studying Laravel installation”, you shouldn’t need to make any changes to the index file.
Let me explain what i did initially and what had done later.
I had installed Invoice Ninja using Softaculous as a normal installation inside my public_html folder on my shared web hosting in a subdirectory called “invoice”.After all, when i called the URL Softaculous instalation wizard provided i got an internal server errror.(https://mydomain.com/invoice)
I had referred few Laravel installation videos on youtube …based on one of the installation guides i had done the below changes.
moved out public folder from invoice folder to pubilc_html folder and made a modification on the index.php of public folder on below two lines,.
I suggest setting up a clean install and then sending us the error details from the logs to help debug the problem. Once you start making changes to the app it puts it in an unknown state which makes it difficult to support.
Note: the Softaculous install should work out of the box, you may want to contact Softaculous directly to ask them.
Thanks Hillel…I will do a clean install now and will share the details soon…Is the subdomain is mandatory to get it works or just install on sub directory also will work…?
I had done fresh install…now the login page is showing below error…no logs in storage folder…!
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@invoice.coastalfresh.in to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Hi Hillel…I did through Softaculous only on my shared hosting cpanel…I did several other apps simple as a matter of minutes…But this made me crazy…!!!
.
Hi I had the same problem when setting up on a subdirectory, just couldn’t get it to work. So I’m now using a subdomain billing.example.com It works so much better.
Hi Zoup… Great…I tried that also…But had no.luck…How is your directory structure.?..All.invoice ninja files on public_html folder?.or outside of that and only public folder inside public_html?.How you point your subdomain root folder?..Pls guide.
Bro I’m using docker so all that is done for me automatically, it was too difficult to set up by hand.
But if i had to guess I would say only the “public” directory should be public (not “storage”). Also I assume from your use of public_html that you’re using apache? I had more luck with nginx.
The way I had it was everything was in /var/www/invoiceninja/ and nginx served /var/www/invoiceninja/public ONLY. Everything else was lcoked down.
But with docker all those problems disappeared, and a subdomain in nginx and docker is easy.
I know it’s not what you want to hear I was in your situation too. That’s why I commented! Good luck
Just rememberd if you using nginx there are also samples in the docker repo on github and it worked for me without any trouble…