January 24, 2020 at 12:40 pm #23291
I’m on self hosted version 4.5.17 but I can’t get the signature system to work.
I get following message after signing and approving the quote/invoice:
Failed to load resource: the server responded with a status of 405 (Method Not Allowed)
Anyone encountered the same problem?January 27, 2020 at 1:27 pm #23316
Hi, are there any details in storage/logs/laravel-error.log or the web server error logs?January 28, 2020 at 2:55 pm #23342
No, nothing at all but I discovered an error in the log file that makes me think that I maybe didn’t do the update like I should.
He’s trying to reach a column that doesn’t exist.
How can I update the database without losing data?
I only copied the documents of the latest version over my 4.5.16 version and nothing else.January 28, 2020 at 3:11 pm #23343
Do you have SSH access? You can run the database migrations using php artisan migrate, otherwise you can load /update in the browser.January 29, 2020 at 4:33 pm #23363
No SSH access and /update isn’t an option.
I’m using Invoice Ninja on a shared hosting, so I don’t have the rights to perform anything I want and /update needs some rights that I don’t have
Isn’t there an update script that I could run?January 29, 2020 at 4:35 pm #23364
Umm… yes, it’s run using /update
Assuming you can’t get SSH access or the permissions enabled one workaround is to copy your database to your local environment, run the migration and then copy it back.January 29, 2020 at 5:16 pm #23365
Is there a difference between the 4.5.16 DB and the 4.5.17 DB?January 29, 2020 at 5:16 pm #23366
No, but my guess would be the database migration failed with a past releaseJanuary 31, 2020 at 9:08 am #23370
In that case the problem isn’t related to the DB.
I’ll try a fresh install to check if it’s related to my installation or to the versionFebruary 1, 2020 at 4:52 pm #23397
I believe I’ve seen this problem in the past, if the database migration hasn’t run the feature fails to work because it depends on the table field to track the value.
One solution would be to setup a new install and transfer the data as JSON, this isn’t ideal though as it isn’t a complete transfer. Alternatively you could copy the database to a system where you have command line access to work through the migrations.February 2, 2020 at 8:11 pm #23401
I’m thinking about moving my data to a VPS so I can get more access than I get now but the problem remains, I still get the 405 error when I try to accept a quote.
I’ve seen somewhere that you suggested that it might be permissions related but for another problem but with the same error message, couldn’t this be the same problem?February 3, 2020 at 7:57 am #23408
We’ve sometimes seen server mod security rules causes issues.
It may help to check that the migrations table is up to date with this listFebruary 4, 2020 at 10:10 pm #23427
Thanks for the tip Hillel!
I don’t think the DB has changed between version 4.5.16 and 4.5.17 (based on your URL), so we can exclude that.
What can be the reason the system won’t accept the signature?
Would it be my fault (hosting) or your fault (coding) ?February 5, 2020 at 6:32 am #23432
Which version are you upgrading from? Was the feature working before you upgraded?February 6, 2020 at 7:27 am #23452
I had 4.5.16 and I uploaded the files of 4.5.17.
I can’t really answer that question because I saw that option only after upgrading to 4.5.17.
I’ve installed the 4.5.16 version locally (through wamp64) but I get the same error.February 7, 2020 at 5:11 am #23467
When testing locally was it a clean install or did you use your database backup?February 7, 2020 at 7:52 am #23469
I did a clean install based on a copy of the 4.5.16 zip fileFebruary 7, 2020 at 9:37 am #23472
Are you still seeing the 405 error? Can you reproduce the problem?
You must be logged in to reply to this topic.