agoodpub wrote: ↑15 Aug 2019, 10:35
Hi I purchased a licence a couple of years ago through the windows store.
If you have purchased FileBot via the Microsoft Store, then you will need to install FileBot via the Microsoft Store. Your Microsoft Account remembers your purchase, so you neither have, nor need, a license file.
That's what I thought, but it only gives me the option to buy it for £33.49 - even though I bought it 2 years ago. Maybe the option I bought was only a fixed-time licence? Except that it was working until I had to do the restore.
If I go to the "Purchased" tab in my account it shows up as been purchased on July 7th 2017.
agoodpub wrote: ↑15 Aug 2019, 16:25
Maybe the option I bought was only a fixed-time licence?
The Microsoft Store / Mac App Store / iOS App Store / Google Play Store all universally only support a simple life-time purchase model. There is no such thing as a fixed-time license, upgrade license, etc. There's no way to cancel or refund a purchase either (for developers at least).
agoodpub wrote: ↑15 Aug 2019, 16:25
If I go to the "Purchased" tab in my account it shows up as been purchased on July 7th 2017.
Please contact Microsoft Support so they can check your account to figure out whats wrong.
agoodpub wrote: ↑16 Aug 2019, 09:08
Thanks for the clarification that it was a one-off payment rather than a yearly subscription.
Yes, I can confirm that, and not just for FileBot, but for ever single application on every single app store platform.
The yearly subscription license model is something that FileBot introduced as an alternative for the store (which is disliked by many) in general, and as a low-cost option for new users that just need FileBot for a few days.
Removed "-u sc-tvheadend" from the command and it worked. admin is the owner of the .license file, so I guess sc-tvheadend doesn't have permissions to overwrite it. Perhaps I should chown it to sc-tvheadend???
Yes, the order of log entries would suggest that it couldn't write the license file in its own application home folder. If the application home folder is not readable / writable, then FileBot can fail in strange an unexpected ways.
On Synology, it's configured to use the same license file by default for all users, and I presume that default location is only writable to the default admin user, but should be readable by all users that execute filebot.
On Synology, there will be a unique application data sub-folder for caches and such for each user, so I don't think you have to change any permissions.
EDIT:
I've updated the Synology package scripts to make sure the .license file is initialized with world-read-writable permissions.
I can't activate my license under my VPS, tested on my local machine and it worked but not on the VPS.. command used filebot --license licensefile.psm
I am on Zorin which is an ubuntu base distribution.
What is the exact command you're using to install the license? Are you sure that you're using a file that is actually a license file? Please PM me the exact license text you're trying to install. You can use the cat /path/to/file.psm command to display the license text.
How did you install FileBot? What version of FileBot are you using? Run filebot -script fn:sysinfo for details.
graveangel wrote: ↑22 Aug 2019, 03:13
When I run the command cat /path/to/file.psm that's what I get.. but if I open the .psm file with a text editor it looks like the picture you posted.
cat is the absolute truth to what the file content is. That is what FileBot sees. That is what all programs see.
You're most likely being confused by some special web interface. You can ask your VPS provider how to upload files, or you can just use scp, or copy & paste into your SSH session.