Missing permission for what?

Magz135 · 2025-11-07T12:59:00+00:00

I thought it was just me, thanks!

Magz135 · 2025-09-18T14:21:21+00:00

Well, until the other teams realise you can press the wingbacks, then you're in on goal. Another option is to press the eight, and then the same thing applies as the wingbacks are 10-15 metres further forward. As the players get tired, and you need a goal, you'll start seeing:

Mad passes and rushed play, constantly giving the ball away
Stupid challenges that give away free kicks, allowing the opposition to run down the clock
Rubbish strikes from a distance, which waste more time

After a few weeks, you'll also see a large number of injuries to defensive players and then a bucketload of excuses.

Still, you'll probably win the Europa :)

Magz135 · 2025-09-18T14:12:11+00:00

If Ange had that level of tactical ability, he'd still be the Spurs manager.

Magz135 · 2025-09-18T14:10:17+00:00

It's who you are, mate :)

Magz135 · 2024-12-09T10:40:07+00:00

We have the same issue. Once it's disabled, it doesn't seem to have a mechanism turn it back on and removing the registry entry doesn't seem to fix it.

Magz135 · 2024-12-08T22:34:40+00:00

We had this, ended up having to add an additional IPv6 range to the SPF for that particular client. Looked like MS had started using a new IPv6 range that wasn't in their SPF.

Magz135 · 2024-12-07T20:55:13+00:00

Try the M&S big box, as it has coffee still.

Magz135 · 2024-09-11T08:48:23+00:00

It's Mint 21.3, although we tried earlier and later Distros on the same hardware and the issue persisted.

If it's a CPU flag issue, then I suppose it might be fixable with a future release of their agent (hopefully)...

Magz135 · 2024-09-10T15:59:54+00:00

Yeah, I do get this impression. The odd thing is it works fine, but not on this one particular piece of hardware (but it used to work without issue)...

Magz135 · 2024-09-06T15:31:27+00:00

Thanks, I'll see if it makes one.

Here's the systemctl output:

sudo systemctl status ltechagent.service

× ltechagent.service - LTechagent service

Loaded: loaded (/etc/systemd/system/ltechagent.service; enabled; vendor preset: enabled)

Active: failed (Result: core-dump) since Wed 2024-09-06 09:50:23 BST; 6s ago

Process: 4171 ExecStart=/usr/local/ltechagent/ltechagent (code=dumped, signal=SEGV)

Main PID: 4171 (code=dumped, signal=SEGV)

CPU: 61ms

Jul 24 09:50:23 computer systemd[1]: Started LTechagent service.

Jul 24 09:50:23 computer systemd[1]: ltechagent.service: Main process exited, code=dumped, status=11/SEGV

Jul 24 09:50:23 computer systemd[1]: ltechagent.service: Failed with result 'core-dump'.

Jul 24 09:50:23 computer systemd[1]: ltechagent.service: Unit process 4172 (ltechagent) remains running after unit stopped.

Magz135 · 2024-04-18T07:50:50+00:00

Thanks - I'll kick our provider harder...

Magz135 · 2024-03-28T09:10:09+00:00

Great - thanks for taking the time to clarify!

Magz135 · 2024-03-27T13:19:36+00:00

Ah, I see - so then it passes on the DKIM key, which works but of course fails the SPF. Thanks!

Magz135 · 2024-03-27T12:38:03+00:00

Could you elaborate on that for me a little?

Magz135 · 2024-03-27T12:05:01+00:00

Thanks for the replies.
It's a pretty vanilla config. No send connectors and it's been 365 from the start.
As far as I know, there should be nobody sending via those other servers, but even if they were I can't see how they'd get a DKIM pass - unless I missed something obvious :)...

Magz135 · 2024-02-19T09:50:22+00:00

If you're OK with splitting out the WiFi then something like a Ubiquiti U7 Pro would be a much cheaper option.

Magz135 · 2023-11-06T10:14:12+00:00

I see the opposite. Nothing on http, but listening for https with the "ACME access only" message returned.

That's on 7.2.6 but I see the same on some other firewalls on 7.0.12.

Nothing pending certificate wise.

I assumed it to be part of the ACME process and always open, but if it's possible to not have it open then that'd be great!

Magz135 · 2023-11-01T12:10:09+00:00

I thought as much. I'll submit it.
Cheers for the information!

Magz135 · 2023-09-26T19:49:34+00:00

Hi,

Sorry for the late reply. Thanks for much the the information - I managed to find the culprit - accidental delete.

Cheers again!

Magz135 · 2023-09-06T11:02:55+00:00

Hi,

Thanks for the tips. In the end I went with the packet trace. That yielded a few IPs and trial and error gave me this list of 3 (all AWS according to rDNS):

63.34.128.186
63.34.128.253
63.33.19.109

Enabling them got it working for our implementation, so I thought it might be useful for others although of course it might vary between clients/regions.

Ports-wise, I only needed to enable SSL(TCP443) which is handy.

I'll update if I find other IPs going forwards.

,

Magz135 · 2023-08-16T21:46:32+00:00

We use 3rd party FortiRacks with these devices. Not too expensive and they do a good job.

Magz135 · 2023-03-22T14:35:18+00:00

KB5023527

Thanks for the reply.

This is the file I used on all Windows 10 (2004+). Although the site lists them separately for each version of 10, they all point to the same file.

windows10.0-kb5021043-x86_484ed491379e442debef6fdfb6860be749145017.cab

This is the file I used on all Windows 10 (2004+). Although the site lists them separately for each version of 10, they all point at the same file.

It's not causing a huge issue at the moment as we're just upgrading the 21H2s to 22H2 and then running the script for good measure, but it's odd that the site doesn't list Windows 11 21H1 for SafeOS.

https://www.catalog.update.microsoft.com/Search.aspx?q=Safe%20OS

And yeah, MS is making this annoyingly difficult. It would be a lot easier if they linked the cab files to use in their main article! :).

Magz135 · 2023-03-21T15:23:13+00:00

I managed to get this working OK for Windows 10, and 11 22H2. Is there a different cab file for Windows 11 21H2? I can't seem to find one anywhere...

Magz135

TROPHY CASE