"something went wrong" and logged out

Self-Hosted | v5
21

OK, thank you very much for your help.
This has baffled me too, as nothing major has changed, yet all used to be OK and a different PC/network it works fine on…
It must be something local to me and not a ninja fault

22

That’s likely a permissions error. Have you verified that your www-data user has full permissions? Have you run the recommended permissions verification on the official InvoiceNinja wiki? Have you verified that your user account has administrator privileges?

23

Hello Northhhill

Thank you for taking the time to reply

It does sound like permissions to me also, but it id work previously
It also works OK with the same user logged in from a different PC/network

I am using a friends hosting company, and it is a shared host at present…
All folders have 755 permissions. i am told the server does not have ‘www-data’ as a user, but however is set to the correct user that has full permissions.

I am logging in as the main user (and sole user), so assume i have admin privileges.
I cannot find out how to check this though. if you could let me know i would be very grateful?

I cannot find the invoice ninja wiki, just the github documentation.
Also am assured the permissions and users have full permissions

  • as said all works OK from my tech support guys pc/network, although i have tried logging in from my mobile on 5G connecting, and i get the same error.
    All i can think is there i a 1 hour time difference from my location to the server, that is in UTC time.

I am really baffled by this, and so is my tech support, as they cannot recreate the error + all used to work fine :frowning:

We will keep looking into this, or maybe if i move to hosted, this would not have issues…

Thanks
Jon

24

An update on this. and the solution

It was down to the server/s and an OWASP3 compliance update, that was blocking external PUT requests.
i dont really know what this means, as my friend owns the hosting company, i am using a “special” shared server at present and their firewalls.

They eventually worked out the problem though.
Hope this may help others

25

Thanks for sharing the solution!

1 Like