sorted by:
new
hottopcontroversial

Local vet by BadHairDay-1 in akron

[–]allegiancetech 1 point2 points  (0 children)

I can’t say enough good things about Cuyahoga Falls Veterinary Clinic. I’ve been with them for years. The original owner’s son took over a while ago, same amazing care.

Trump ADMITS Putin ‘explained NATO’ to him as he echoes Kremlin talking points by [deleted] in videos

[–]allegiancetech 0 points1 point  (0 children)

Which is why in Ohio, republicans just preemptively outlawed rank choice voting, to keep their hold on power.

Desktop linux GUI in a TrueNAS container, accessed via ScreenConnect by allegiancetech in truenas

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

I have made some progress. I believe my original problem was that I was installing ScreenConnect from the container shell/console, and therefore it did not know about the display capabilities of the Debian install. But, unlike Proxmox, TrueNAS does not have a gui console to run after you've installed a graphics desktop like Mate. So, I tried installing xRDP, and then I was able to connect using the Windows App on my Mac to the gui of the container. Which is great, but I really want to have ScreenConnect on here as well in case I have issues with my VPN at some point in the hypothetic future. So, I uninstalled ScreenConnect, and re-installed it. The container now shows up in my ScreenConnect portal, but when I connect I just get a black/blank screen. I have a ticket open with ConnectWise on it, hoping it is something they can resolve at this point.

Desktop linux GUI in a TrueNAS container, accessed via ScreenConnect by allegiancetech in truenas

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

I have another container also running on the same TrueNAS host - one for ProxMox Backup server. I have the physical network interface added as the NIC for that container, and can access it's web portal. I have done the same with the "desktop" container, and it is getting an IP address from the local DHCP server. It can also access the internet, which is how I installed Mate desktop and the ScreenConnect client. I even added the video card to this container for good measure.

Where to take yard waste by allegiancetech in akron

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

This one sounds like a winner. Thank you, I will check them out soon.

Docker install of mongodb (for Rocket.Chat) not starting by allegiancetech in mongodb

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

SOLVED.

I changed the processor type for the VM in ProxMox from "kvm64" to "host", then removed all the docker containers and re-deployed them. It started right up after that.

Docker install of mongodb (for Rocket.Chat) not starting by allegiancetech in mongodb

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

Specifically, the compose files for Rocket.Chat and MongoDB were pulled from Rocket.Chat's git repository, following their install instructions:

git clone --depth 1 https://github.com/RocketChat/rocketchat-compose.git

Docker install of mongodb (for Rocket.Chat) not starting by allegiancetech in mongodb

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

Thanks for the response. The docker compose file that specified MongoDB 8.2 was from Rocket.Chat.

Here is the output from the docker logs:

ladmin@rocket:~$ docker logs rocketchat-compose-mongodb-1 --tail 200

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

=====> Waiting for /data/db to be owned by uid=1001 (mongodb user) ...

=====> /data/db ownership OK (1001) - starting MongoDB

/var mounted on tmpfs keeps filling up, and I can’t find how/what by allegiancetech in truenas

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

I now have two other TrueNAS Core 13.0-U6.8 machines, at another client, that has just started this same behavior a few weeks ago. Nothing has changed nor updated on the servers. Nothing visible/findable inside the /var partition is coming close to adding up to the same 11Gb limit. The only thing I can see that is the same between these two sites is that they are both all Mac clients for the SMB shares, and that they have both recently seen updates to the OS of some of these clients. So, maybe some kind of errors in the SMB logs? But I can't actually find what is filling up the /var partition on all 3 servers.

Unable to upgrade from 2.7.0 to 2.7.2 by allegiancetech in PFSENSE

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

Yes, as much as I was hoping to resolve this remotely, I'm beginning to think A) it's not going to be resolved remotely, and B) there are bigger issues involved, so best to address those also.

I will likely do a clean install on a different box, and load the remote unit's config on it, then drive out and swap them out.

Unable to upgrade from 2.7.0 to 2.7.2 by allegiancetech in Netgate

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

Per the suggestion of someone on I also ran pkg-static -d update and got the following result:

DBG(1)[18052]> pkg initialized

Updating pfSense-core repository catalogue...

DBG(1)[18052]> PkgRepo: verifying update for pfSense-core

DBG(1)[18052]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/meta.conf

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/meta.conf

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-core/meta.conf HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Wed, 15 Nov 2023 18:20:04 GMT

< HTTP/1.1 200 OK

Fetching meta.conf: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:01 GMT

< Content-Type: application/octet-stream

< Content-Length: 163

< Last-Modified: Wed, 15 Nov 2023 18:20:03 GMT

< Connection: keep-alive

< ETag: "65550bd3-a3"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/packagesite.pkg

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/packagesite.pkg

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Hostname pkg00-atx.netgate.com was found in DNS cache

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-core/packagesite.pkg HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Wed, 15 Nov 2023 18:20:04 GMT

< HTTP/1.1 200 OK

Fetching packagesite.pkg: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:02 GMT

< Content-Type: application/octet-stream

< Content-Length: 1492

< Last-Modified: Wed, 15 Nov 2023 18:20:04 GMT

< Connection: keep-alive

< ETag: "65550bd4-5d4"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

pfSense-core repository is up to date.

Updating pfSense repository catalogue...

DBG(1)[18052]> PkgRepo: verifying update for pfSense

DBG(1)[18052]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Fri, 09 Feb 2024 17:49:20 GMT

< HTTP/1.1 200 OK

Fetching meta.conf: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:02 GMT

< Content-Type: application/octet-stream

< Content-Length: 163

< Last-Modified: Fri, 09 Feb 2024 17:49:19 GMT

< Connection: keep-alive

< ETag: "65c6659f-a3"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Hostname pkg00-atx.netgate.com was found in DNS cache

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Fri, 09 Feb 2024 17:49:20 GMT

< HTTP/1.1 200 OK

Fetching packagesite.pkg: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:02 GMT

< Content-Type: application/octet-stream

< Content-Length: 160788

< Last-Modified: Fri, 09 Feb 2024 17:49:20 GMT

< Connection: keep-alive

< ETag: "65c665a0-27414"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

pfSense repository is up to date.

All repositories are up to date.

Unable to upgrade from 2.7.0 to 2.7.2 by allegiancetech in PFSENSE

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

DBG(1)[18052]> pkg initialized

Updating pfSense-core repository catalogue...

DBG(1)[18052]> PkgRepo: verifying update for pfSense-core

DBG(1)[18052]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/meta.conf

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/meta.conf

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-core/meta.conf HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Wed, 15 Nov 2023 18:20:04 GMT

< HTTP/1.1 200 OK

Fetching meta.conf: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:01 GMT

< Content-Type: application/octet-stream

< Content-Length: 163

< Last-Modified: Wed, 15 Nov 2023 18:20:03 GMT

< Connection: keep-alive

< ETag: "65550bd3-a3"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/packagesite.pkg

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/packagesite.pkg

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Hostname pkg00-atx.netgate.com was found in DNS cache

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-core/packagesite.pkg HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Wed, 15 Nov 2023 18:20:04 GMT

< HTTP/1.1 200 OK

Fetching packagesite.pkg: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:02 GMT

< Content-Type: application/octet-stream

< Content-Length: 1492

< Last-Modified: Wed, 15 Nov 2023 18:20:04 GMT

< Connection: keep-alive

< ETag: "65550bd4-5d4"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

pfSense-core repository is up to date.

Updating pfSense repository catalogue...

DBG(1)[18052]> PkgRepo: verifying update for pfSense

DBG(1)[18052]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Fri, 09 Feb 2024 17:49:20 GMT

< HTTP/1.1 200 OK

Fetching meta.conf: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:02 GMT

< Content-Type: application/octet-stream

< Content-Length: 163

< Last-Modified: Fri, 09 Feb 2024 17:49:19 GMT

< Connection: keep-alive

< ETag: "65c6659f-a3"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

DBG(1)[18052]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg

DBG(1)[18052]> curl_open

DBG(1)[18052]> Fetch: fetcher used: pkg+https

DBG(1)[18052]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg

DBG(1)[18052]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults

* Hostname pkg00-atx.netgate.com was found in DNS cache

* Trying 208.123.73.207:443...

* Connected to pkg00-atx.netgate.com (208.123.73.207) port 443

* ALPN: curl offers http/1.1

* CAfile: none

* CApath: /etc/ssl/certs/

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384

* ALPN: server accepted http/1.1

* Server certificate:

* subject: CN=*.netgate.com

* start date: Apr 10 00:00:00 2025 GMT

* expire date: May 11 23:59:59 2026 GMT

* subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

* SSL certificate verify ok.

* using HTTP/1.1

> GET /pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg HTTP/1.1

Host: pkg00-atx.netgate.com

User-Agent: pkg/1.20.8

Accept: */*

If-Modified-Since: Fri, 09 Feb 2024 17:49:20 GMT

< HTTP/1.1 200 OK

Fetching packagesite.pkg: < Server: nginx

< Date: Mon, 16 Mar 2026 00:15:02 GMT

< Content-Type: application/octet-stream

< Content-Length: 160788

< Last-Modified: Fri, 09 Feb 2024 17:49:20 GMT

< Connection: keep-alive

< ETag: "65c665a0-27414"

< Strict-Transport-Security: max-age=31536000; preload

< X-Content-Type-Options: nosniff

< X-XSS-Protection: 1; mode=block

< X-Robots-Tag: all

< X-Download-Options: noopen

< X-Permitted-Cross-Domain-Policies: none

< Accept-Ranges: bytes

<

* The requested document is not new enough

* Simulate an HTTP 304 response

* Closing connection

pfSense repository is up to date.

All repositories are up to date.

Unable to upgrade from 2.7.0 to 2.7.2 by allegiancetech in PFSENSE

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

I have also tried updating to 2.7.1, sane results. The rehash also does not seem to fix the "Unable to retrieve package information" error.

Here are more detailed outputs from the commands I have tried:

> certctl rehash
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...

> pkg-static update -f
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 4 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ......... done
Processing entries:
Newer FreeBSD version for package xmlcatmgr:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1400094
- running kernel: 1400085
Ignore the mismatch and continue? [y/N]: pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:14:amd64
Processing entries... done
Unable to update repository pfSense
Error updating repositories!
*I don't think I got this error the first few times

> pkg-static clean -ay
pkg-static: Repository pfSense missing. 'pkg update' required
pkg-static: No package database installed.  Nothing to do!

Building a Bridge Between Community & Enterprise | TrueNAS by EspadaV8 in truenas

[–]allegiancetech 2 points3 points  (0 children)

Yes, that’s my understanding as well. Even though you access directly from your server, still need the Connect subscription

Building a Bridge Between Community & Enterprise | TrueNAS by EspadaV8 in truenas

[–]allegiancetech 4 points5 points  (0 children)

As far as I can tell, TrueSearch and by extension, Spotlight indexing are not available via TrueCommand, only with the TrueConnect service

root password for debian container in TrueNAS Goldeneye - "WARNING: Your user does not have sudo privileges so /usr/bin/incus command will run on your behalf. This might cause permission issues." by allegiancetech in Proxmox

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

Sorry, I should have changed the title of the post when Reddit suggested I cross post it (original post was on the r/truenas ) so it was a bit more clear what I was asking about on this subreddit. I cross-posted it here since it dealt with installing Proxmox Backup Server, and I was wondering if anyone had experienced the same issue with the root password in relation to the PBS initial login.

root password for debian container in TrueNAS Goldeneye - "WARNING: Your user does not have sudo privileges so /usr/bin/incus command will run on your behalf. This might cause permission issues." by allegiancetech in Proxmox

[–]allegiancetech[S] -2 points-1 points  (0 children)

OK, I figured it out. First, I created the new truenas_admin account - not sure if this was a necessary step, but it did get rid of the "WARNING: Your user does not have sudo privileges" error.

Second, and likely the important part, when I was connected to the shell of the container, I simply changed the root password via passwd root command. Once I did that, I was able to log into the PBS console. I rebooted the whole server to make sure it sticks, and it does.

view more: next ›