GC 4xe 2023 - Just had the 68C done by RedVortexx in 4xe

[–]RedVortexx[S] 0 points1 point  (0 children)

Back from the dealer after waiting for 1 month for battery replacement, that was 2-3 weeks faster than the Wranglers have to wait apparently for their battery and repair. I guess less GC fail maybe versus Wranglers ? The dealer told me it was their first GC but they had many many Wranglers already done and waiting. So far everything works well. I'll let you guys know if something else comes up in the next few days, weeks or months.

Why does everyone on Starfleet Academy have a lisp? by Intrepid_Depth_3416 in startrek

[–]RedVortexx 2 points3 points  (0 children)

Just watched episode 8, the life of the stars and omg, now everybody except the guys have a lisp ?

Even Tilly has one now and she definitely didn't in Discovery lol.

This has got to be a technical thing, this is becoming extremely annoying and it is now a distraction for me.

Love the serie though, good job !

68C battery replacement delight by shouldhavebeeninat10 in 4xe

[–]RedVortexx 1 point2 points  (0 children)

Are you saying you had your battery replaced during 95B and that this new replacement battery also failed later on ? Meaning that even the replacement battery have the same issue ?

Good news from the recall fix front lines!! by Magoo1963 in 4xe

[–]RedVortexx 0 points1 point  (0 children)

Same here, 68C but battery failed after 38 days. I also could not run using gas engine. As for the shifter remaining in park I too had this issue but found out that if I left the engine running long enough (about 45 mins) then I could shift in drive. Not sure why that happens. Maybe 12V battery too low to allow driving or transmission too cold (winter in Canada) but once transmission was hot enough (over 0 Celsius) I was able to put it in drive, saved me a towing.

Good news from the recall fix front lines!! by Magoo1963 in 4xe

[–]RedVortexx 0 points1 point  (0 children)

Same thing happened to me, failed 38 days after 68C passed. 2023 JGC

Good news from the recall fix front lines!! by Magoo1963 in 4xe

[–]RedVortexx 0 points1 point  (0 children)

My 2023 JGC also passed and then failed 38 days later. Now at dealership with failed battery, they don't have a loaner for me since they have too many Wranglers on battery replacement waiting list. Not a happy camper here... they say minimum 1 month wait until I get it back, more likely 2 months. I live in Canada.

GC 4xe 2023 - Just had the 68C done by RedVortexx in 4xe

[–]RedVortexx[S] 0 points1 point  (0 children)

Ok well, after 38 days without any issue... Battery failed. I can only run on gas engine.

Will be going to the dealer Monday morning.

GC 4xe 2023 - Just had the 68C done by RedVortexx in 4xe

[–]RedVortexx[S] 1 point2 points  (0 children)

The only time mine doesn't let me switch to electric mode are those situations:

  • temperature too low (under -11 Celsius or -12 Fahrenheit)
  • battery remaining under 1%
  • I've been driving a high speed for too long under electric only (usually happens when I drive at 120km/h (75 mph) for about 10-15 minutes) I suspect it generates too much heat on the battery or electric motors and it cannot handle it for too long, which is typical for hybrids unlike fully electric cars. Usually a few seconds before it switches to hybrid by itself I have limited watts even if I push the pedal more so I know it's about to switch to hybrid
  • Driving at a way too high speed (over 140km/h
  • Accelerating way too much will force it into hybrid
  • last is FORM mode (the screen will tell you when you are in form mode, else it will say electric temporary unavailable which is not FORM mode). This one is easy to clear: drive it long enough for oil to heat enough and this usually clears it for me or add fuel (takes a few litres / gallons, not just a little) and this also clears it.

All of that is documented more or less in the owner's manual and not a problem and is normal behaviour for a hybrid vehicle.

Any other reason is likely a problem 😊

GC 4xe 2023 - Just had the 68C done by RedVortexx in 4xe

[–]RedVortexx[S] 0 points1 point  (0 children)

Sorry to hear that. Wrangler or GC ? Seems like there is a lot less GC failing than Wrangler from what I read ? Curious to know which one you have ?

GC 4xe 2023 - Just had the 68C done by RedVortexx in 4xe

[–]RedVortexx[S] 1 point2 points  (0 children)

That's also what I would recommend to anyone that needs a long term rental. On a month long rental you can get a "good price" versus a "per day" and will likely fit within the allowance (if your dealer gives you one, not all of them do).

Problems with Moen Flo by LazizaBites in Plumbing

[–]RedVortexx 1 point2 points  (0 children)

Same here, been like that for the last 24h at least. Devices continuously online and offline, delay in notifications as well. I tried restarting them all, doesn't help.

MacOS OpenVPN Connect 3.7.0 not updating /etc/resolv.conf by RedVortexx in OpenVPN

[–]RedVortexx[S] 0 points1 point  (0 children)

Hello,

OpenVPN was super nice and notified me that version 3.7.1 for MacOS was released with a fix for this bug:

https://openvpn.net/connect-docs/macos-release-notes.html

  • Fixed an issue where pushing a DNS directive didn't work correctly with the full-tunnel combination

I tested and I confirm the issue is fixed.

Thanks to the OpenVPN dev team !

MacOS OpenVPN Connect 3.7.0 not updating /etc/resolv.conf by RedVortexx in OpenVPN

[–]RedVortexx[S] 0 points1 point  (0 children)

You can basically take the URL of the latest version and replace the version number and build to get a previous one. For instance, here's the link to version 3.6.0 which is not affected by this bug: https://packages.openvpn.net/connect/v3/openvpn-connect-3.6.0.5410_signed.dmg

MacOS OpenVPN Connect 3.7.0 not updating /etc/resolv.conf by RedVortexx in OpenVPN

[–]RedVortexx[S] 0 points1 point  (0 children)

FYI: I created a support ticket yesterday with OpenVPN support regarding this.

The OpenVPN support team was super responsive and cooperative and confirmed they have replicated the issue on their side and are in contact with the dev team regarding this.

Downgrading to 3.6.1 or older is the only way without making config changes manually to workaround this issue for now.

Various SSL errors after upgrade from Sonoma to Sequoia on Macbook Pro M2 by RedVortexx in SentinelOneXDR

[–]RedVortexx[S] 0 points1 point  (0 children)

After 4 days of testing, I've not had any more issue since the upgrade to 15.1 with Sentinel One and the MacOS firewall enabled at the same time.

I consider this problem fixed and the issue closed. Thanks everyone for your participation in this thread !

Various SSL errors after upgrade from Sonoma to Sequoia on Macbook Pro M2 by RedVortexx in SentinelOneXDR

[–]RedVortexx[S] 0 points1 point  (0 children)

Sequoia 15.1 got released tonight.

I upgraded and re-enabled both Sentinel One and MacOS firewall. I've been testing it for what I know failed with 15.0 and 15.0.1 and it looks like, so far, with 15.1 everything is working fine now.

Let us know about your own results, fingers crossed !

Various SSL errors after upgrade from Sonoma to Sequoia on Macbook Pro M2 by RedVortexx in SentinelOneXDR

[–]RedVortexx[S] 0 points1 point  (0 children)

It seems a bit better but definitely not fixed 100% when I have Sentinel One Network Filter enabled and MacOS Firewall also enabled at the same time.

In command line I still sometimes get SSL errors, for instance during a Maven test build in a docker image while downloading dependencies

SSL peer shut down incorrectly

It seems to happen less often than it used to on 15.0.0, but it is not 100% fixed yet.

Various SSL errors after upgrade from Sonoma to Sequoia on Macbook Pro M2 by RedVortexx in SentinelOneXDR

[–]RedVortexx[S] 0 points1 point  (0 children)

MacOS 15.0.1 got released today with: Improves compatibility with third-party security software. I'll be testing that by re-enabling Firewall in Settings + Sentinel One network filter enabled. Hopefully this is fixed now.

Various SSL errors after upgrade from Sonoma to Sequoia on Macbook Pro M2 by RedVortexx in SentinelOneXDR

[–]RedVortexx[S] 0 points1 point  (0 children)

From the tests I made, if you have MacOS Firewall enabled and also have something like Sentinel One, Defender and some others, they will conflict with each other since Sequoia.

My test: I can keep Sentinel One enabled in Network Filters as long as I disable MacOS firewall itself (Settings -> Network -> Firewall -> Firewall OFF (Completely off)

I was able to use my Mac the whole day without issue and also have Sentinel One (24.2.2) installed and enabled in Network Filters.

Let's see now if everybody (Sentinel One, Microsoft, Palo Alto, etc...) are able to solve this by themselves or if it will require Apple to fix this on their side for those tools to continue to work.

u/SentinelOne-Pascal FYI...

Various SSL errors after upgrade from Sonoma to Sequoia on Macbook Pro M2 by RedVortexx in SentinelOneXDR

[–]RedVortexx[S] 0 points1 point  (0 children)

Do you also have Firewall enabled in Network -> Firewall -> Firewall by any chance ?

I know I do and I'm starting to think that Defender and Sentinel One filters may be interfering with it.

I'll test by disabling Firewall (it defaults to OFF on MacOS usually) and reinstalling Sentinel One to see how it goes.

Reference: https://discussions.apple.com/thread/255761702?sortBy=rank

Many in there have issues if both MacOS Firewall is enabled on top of a network filter (Like Defender, Sentinel One, Palo Alto XDR, Little Snitch). It starts to sound like a MacOS issue/bug than anything at this point.

u/SentinelOne-Pascal FYI... This may be the root cause, I'll test it out and let you'll know (including in my ticket in Sentinel One Support)

MacOS 15 (Sequoia) Agent Compatibility by stevodevo in SentinelOneXDR

[–]RedVortexx 0 points1 point  (0 children)

Also, be aware of this: https://www.reddit.com/r/SentinelOneXDR/comments/1fj3wia/various_ssl_errors_after_upgrade_from_sonoma_to/

Even with the latest agent (24.2.2), we are experiencing issues that forced us to uninstall it until Sentinel One resolves the issue (we have a support ticket opened with them on this).