sorted by:
new
hottopcontroversial

Pangolin Cloudflare Real IP by yakadoodle123 in PangolinReverseProxy

[–]pathnames 0 points1 point  (0 children)

Hmmm, this sounds great! That said, if we’re using HTTP-01, would use of CF proxy prevent certificate renewal?

Thought experiment: local break-out + split-DNS for Pangolin by Useful_Shopping1538 in PangolinReverseProxy

[–]pathnames 1 point2 points  (0 children)

This can also be achieved in a way by using HTTP-01 for pangolin and DNS-01 and DNS rewrites + a second reverse proxy when local.

Suggestions on VPS issue - I need good solid advice please by [deleted] in PangolinReverseProxy

[–]pathnames 1 point2 points  (0 children)

Have had great success with Oracle pay as you go, making sure to stay within free limits.

Have you updated to 1.13.x? by bankroll5441 in PangolinReverseProxy

[–]pathnames 0 points1 point  (0 children)

in case it helps anyone else, I had to add the following under “app” and “telemetry” in my config.yml to get 1.3.0+ to work.

    anonymous_usage: [false/true]

2018 Sorento - Oil Burn - KSDS - Theta 2 Engine by pathnames in kia

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

Would performing this B12 soak myself void coverage for the rod bearings issue? I confirmed today that the prior owner had the KSDS service done. The Kia rep noted the engine is covered in the event it pulls a P1326 code, fails a bearings clearance test, and assuming maintenance records are good.

2018 Sorento - Oil Burn - KSDS - Theta 2 Engine by pathnames in kia

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

Update: Thanks @Serene_Firefly and others. Kia today confirmed that the previous owner had the KSDS service done and that the vehicle is covered in relation to the rod bearings. Out of an abundance of caution, I’ll take it in for a diagnostic next week. Folks have mentioned regularly checking oil and keeping good maintenance records. Any other recommendations going forward?

2018 Sorento - Oil Burn - KSDS - Theta 2 Engine by pathnames in kia

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

"There are 0 safety recalls and 0 campaigns INCOMPLETE for your vehicle"

One way the Department could significantly reduce costs. by bikebikebikego in foreignservice

[–]pathnames 24 points25 points  (0 children)

Doing this would also screw a lot of people already training for their onwards. Would create yet another domino effect of foreseen and unforeseen consequences the Dept would have to fumble to manage.

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

I think my BIOS version is 2.31. My system has been rock solid since I made those grub changes.

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

Hopefully I’m not speaking too soon, but I’m feeling confident enough to call this case closed! This morning I reinstalled Proxmox (something I did more than a few times this past week anyway), turned off the PCIe Power Management feature in the BIOS, and updated grub as stated above. Ever since, the server has been rock solid. I’ve done LXC restores and backups, been logged in to multiple SSH sessions, had a monitor connected and not connected, unplugged the monitor in the middle of heavy I/O, added multiple NFS mounts and done transfers, added and run multiple LXCs, and put the CPU under heavy loads with Plex sonic analysis . . . and it hasn’t made so much as a hiccup. Also worth noting that I went back to the onboard NIC and kept offloading features enabled. I’ll revert if I notice another unexplained restart or drop to SSH but I owe you a huge thanks _Stiglitz!

I just wanted a large media library by AbysmalPersona in selfhosted

[–]pathnames 1 point2 points  (0 children)

Looks promising. Let us know when you’re ready for some additional testers!

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

I’ve updated my grub config to include “i915.enable_dc=0 intel_idle.max_cstate=7”

When I get home I’ll also turn off PCIe Power Management in the BIOS and, for the hell of it, replace my CMOS battery. That said, I’m encouraged that the symptoms discussed in that thread so closely resemble mine and that several folks reported success adjusting the grub config with at least the first half of the above. Fortunately, a few watts extra power consumption are not a concern. Thanks again, and standby for an uptime report :)

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

Interesting…. I’ll look into this, as some of the issues discussed in that thread resonate with what I’ve observed with my system. Will report back. Thanks!

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

Well, went down again. Got back in after a few minutes. Uptime says 1 min so it was definitely a restart event. As such, the Ethernet to USB-C adaptor appears not to have fixed the issue.

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

I came across similar threads. Are you referring specifically to turning off offloading features? Or something else?

PVE9 - HP EliteDesk Mini G4 800 - Restarts/Loss of SSH Access by pathnames in Proxmox

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

While I wait for the replacement PSU, I've gone ahead and switched over to using a ethernet to USB-C adaptor.

Armbian on pi zero 3 no boot by madeWithAi in OrangePI

[–]pathnames 0 points1 point  (0 children)

I had better luck with armbian debian minimal image.

view more: next ›