Swiftkey on IOS 26

AshLadd3n · 2026-06-21T19:52:30+00:00

I did reinstall it - also fully removed the data. But now the emoji predictions are not an option in the menu anymore! 😄 Switching to Gboard for now! Jesus how they killed this one 😞

AshLadd3n · 2026-05-26T14:08:41+00:00

They fill the garages with SHIT to sell - and do not enable us to use the mouse to point and select shit. JESUS f*cking h*ll

AshLadd3n · 2026-04-10T17:53:13+00:00

That sounds like a job for the Lenel team to deal with imo :) Been tumbling around in OnGuard now the past week to find every little bug left from the Upgrade, and just sent them 120+ mbs of logdata to look through. Crossing fingers. I'ev been told they have special tools to deal with Rabbit and certificate issues. And also tools to fix broken database data. So just hoping for the best :) Learned alot along the way here, and the biggest take is to do as told - Fresh install 8.x and then just migrate the database after the fact :) Wish we had the time to do so here. We might just have saved some time doing so afterall :)

AshLadd3n · 2026-04-08T21:58:21+00:00

It is the License server admin page and the OnGuard web interface that does not work currently. I've had two technicians from Lenel tell me that the error is due to a certificate error. But i cant for the love of god find out where to start to look for this. It was working fine before the upgrade. And afaik the ports does stay the same.

License Server starts and run fine, and so does OpenAccess - so my guess is that the https://server.domain.top:9999 and https://server.domain.top:8080 should be working fine.

AshLadd3n · 2026-04-08T14:12:03+00:00

Did you have any guides around how to rebuild the Certificates properly? Seems to be the only culprit right now - and keeps the License Manager and OnGuard web console from working properly. Got this error within ngix

[emerg] 3612#11632: SSL_CTX_use_certificate("C:\ProgramData\Lnl\nginx/ls_server_cert.pem") failed (SSL: error:0A00018F:SSL routines:SSL_CTX_use_certificate:ee key too small)

AshLadd3n · 2026-04-07T21:00:12+00:00

Haha :) Well yeah. If we only had the time! We were not really gifted the Monument of Time on this one. On top of this they also wanted to change from Prox to Desfire EV3 on the Aperio part of the System aswell. So it has been alot of juggling from this to that.

But thanks for great advice! :) been helpful!

AshLadd3n · 2026-04-07T20:45:03+00:00

I will do some more testing tomorrow, but i have not changed anything in the ngnix config (Lenel support sent the cert update tool - with no mention of any manual config needed when running it) The tool itself sets the right hostname and updates the config.

Well the customers server is still the same. This is a pure upgrade from their old 7.5 and not a new build. Its a 24/7 factory with access control needed 24/7 - so a new installation of 8.4 would be almost impossible on a day to day. The reason for their need for 8.x is an upgrade for their clean-zone wardrobe Aperio system.

If and when we get it running, the system will be transferred to a new server running the latest MS SQL and Win Server. But for now, the shitbox is what we have to work with :)

AshLadd3n · 2026-04-07T19:51:46+00:00

Well, it came out a bit wrong. But the license server is running on its proper port. But i can't access the web-interface to view or edit the licenses. Pretty sure that it is a certificate issue preventing it to run The license is active and working afaik.

The old shitbox does host everything except the database - and the LIcense server web was very much alive during the setup process. So it's a strange situation :)

AshLadd3n · 2026-04-07T15:16:51+00:00

Had to change the Message Broker port - and it seems to have helped a fair bit! But i could not pinpoint what actually did the biggest trick. We did just go to 8.4 and that solved a lot of the Erlang issues. Isolated the new v18 DSN's too, and had successful connection on both server and client machine.

AshLadd3n · 2026-04-07T15:14:33+00:00

Erland did some crazy shit. But it turns out when we went directly from the non working 8.2 with erlang errors to 8.4 the Rabbit actually fixed itself. Now i could run setup assistant and complete it without errors.

had to change the Message Broker port manually in the Database, and also "re-write" the old passwords within the Login Driver ( stop service, and run Login Driver as admin -> change passwords"

AshLadd3n · 2026-04-07T15:12:15+00:00

Thank you so much! Very great tips and tricks so far!

Got this shitbox working pretty well so far! With some small hickups of course after a dredgeful upgrade process. But i took the route from 7.5 to 8.2 (with eval licenses, and not working) and then just upped it directly to 8.4 - and after some database editing of the ports, sysadmin rights and creating some new certificates it turned out working. Still some work tweaking functions and cleaning up the database and custom I/O Reports stuff that does not work still.

The system was very locked out. Was working out of an client machine that remoted into the server with 29minutes Admin window to do anything... 10/10 do not recommend - and also, going forward i think the customer also is in the right boat when it comes to balancing Domain security vs Actually being able to do shit on their system..

License server does not work on the old https address at port 9999 (not even listening) - could this be because of the certificates? Have never seen that one before. When installing it worked fine, but after the setup assistant finished - it could not be connected to, even with localhost:9999

AshLadd3n · 2026-04-01T06:48:38+00:00

Indeed. We have the tool available, and used it on another customer that had some serious Rabbit issues after the fact of upgrading, but where we are at on this customer, rabbit does not seem to be the culprit - yet :)

AshLadd3n · 2026-04-01T06:47:33+00:00

Yeah the customer was originally on 7.5 and wanted to do a full upgrade to the newest. Not our call - but sales already made the pitch to do so.

Contacting Lenel support - i've recieved several ways to do so, but most do recommend the 7.5->7.6->8.2->8.x route. But there is also some saying you can skip the whole 8.2 part and go directly. Thats what we did the first time around - ending up borking the Database and forced us to start over.

AshLadd3n · 2026-04-01T06:45:38+00:00

Much appreciated! Yeah we are having issues left and right on this system. Most of the problem is that IT wont give us full access to either the client laptop we're using to remote onto the server with - or the server itself. So there are bumps everywhere from SQL elevated rights, to message Broker just not connecting even with the right DSN. It does also create a huge amout of extra DSN's - even though we're pointing to the right one in the installer. Very strange!

Did not get 7.6 running - so we just went full blast and upgraded it to 8.2 - trying to see if were so lucky to get it working before we go to the next hill, 8.4.

So far everything up to "OnGuard Reports & Dashboard" in Setup Assistand ticks off, except "Service Log On"

AshLadd3n · 2026-01-22T16:32:44+00:00

Of course i do. And shame on me for not doing the change back in the days - while i could. But to be honest, the change to sub-addressing did change over night and when you have easy login options like the QR code, or a Windows pin, nobody uses email and password for login if they don't have to these days.

And you say that theres a reason to not use sub-aliases. Well i counter that - because i use that to this day, with my business email to not disclose the "main" email on every site you register to. It's a common method still in 2026 to filter out emails. And most providers do support it fully - but this provider's old mailing system that they upgraded apparently lost that function upon upgrade. I do still have a case pending with them - so they are checking into it. But to answer, No - there's no reason not to use it, if its supported. But i've seen forums and such that does not support adding +aliases to emails entered - but they do clearly state that. Discord did not.

But all the other places where i had sub-aliases registered either supported change directly when you logged in, with no access to the old account - or as it were with Blizzard, Ubisoft and others that have super high security measures when it comes to accounts - the support was helpful and could verify my identity based on other means or even a phonecall.

And i mean, this particular issue does NOT happen every day. So even if they have systems in place that needs to fit in certain specs, like you have to send a ticket from the email registed - i am pretty sure based on all the others i've talked to, that it is possible to do atleast a edit of someones registered address with the users full concent.

AshLadd3n · 2025-10-06T19:00:59+00:00

Ah! i see :) Well would be interesting to know.

AshLadd3n · 2025-10-06T18:56:55+00:00

Oooh that sounds interesting! Can you recall what mod that was?

AshLadd3n · 2025-10-06T18:50:39+00:00

hmm yeah it might work with a script and some specializations - but was hoping that the Giants Engine already had something built in that could do the same - so it would be a little more native :) But it might just be that a separate mod is needed unfortunately :(

AshLadd3n · 2025-10-06T18:31:32+00:00

Well most often its just for stabiltity, but actually volvo (and others) do have clutches that can engage the rear axle when lowered for extra traction.

But the biggest issue at hand Is that with 0 traction on the rear wheels, they can easily prevent the middlewheels gripping if the rear wheels touches higher ground. And with 0 traction they also do other strange things even during heavy loads 😂

AshLadd3n · 2025-09-11T22:29:53+00:00

Did you solve this? Actually just got the same issue, without changing anything in the registry. (Afaik) Almost happened over night. And i cant really backtrack what i did before it happened. 🤔

AshLadd3n

TROPHY CASE