I am unable to link my device ID to my Community account. When I put in the string that is in FydeOS Settings…Subcription Information it will not save. If I refresh the string is not saved.
I am now unable to edit anything in my Community account. This happened once I got my trust level upgraded to Basic. I get the below error when I try and go to Preferences or Activate Patron or any other menu item under that secion.
I also get the problem
solve this pls
@alpha
Still problem for me too, on virtually all pages that are related to me on the community pages.
At first I thought it was because I had double posted and was banned, but I don’t think so now 
I am now able to get into my prefrences page but I still can’t click on the Activate Patron section. It still takes me to the same Oops! That page doesn’t exist or is private page. @alpha can you please give us an update on this.
Well now after installing 19.0 on an old Intel CPU with iGPU I managed to get something to work that did not work from a Linux webbrowser earlier. Clicking listing my posts for example. That always gave me a OOPS message before. Not yet tested much other as I wont register for this old machine. Just a test. Finally a computer without the red tint problem too. Intel G2030.
EDIT: YAY it seems my community pages bugs are gone now !! Maybe time to try on the laptop and register this stuff soon 
working on fixing the community these days - Discourse doesn’t make our lives easy
1 Like
Luckily most of the bugs I found in my problems are fixed ! I have not yet registered myself as a paying customer but that hopefully is coming up soonish ! Hopefully the red tint bug will be gone soon on my laptop too ! However I managed to get the software running on an old Pentium G2030 with iGPU and running quite well for my modest demands ! Anyway good luck going forward, this could be great !
@alpha this seems to be fixed now. Thanks for the help getting this resolved. One last question how do you create technical support tickets?
we are cooking a separate support ticketing system for this purpose, building it on top of Discourse was a mistake after all. Hang tight, it will be there soon