@victorrhoden00 reinstall the package remove that file redownload the black list

@parry said in packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0:

Does this mean 2.6 is no longer supported

2.6 is no longer supported

https://docs.netgate.com/pfsense/en/latest/releases/versions.html

@johnpoz Ahh.. Thanks. Will look in to those.

@keyser i think i understood this in the first place, the thing is that from all the videos and the guides that i watched and tried i cant semm to understand where to import the pf sense host to send the data.

@keyser thank you that fixed it

This post is old but for anyone interested, I confirm the issue too: with RAM Disk, ntopng configuration is reset when a "normal" reboot of pfSense occurs (even if Periodic RAM Disk Data Backups is set).

pfSense v2.7.2-RELEASE package ntopng v0.8.13_10 in pfSense (ntopng-5.6)

And contrarily to what I read in other posts questioning usefulness of RAM Disk settings, from my limited understanding, I think it's quite useful on my setup: I have a "low cost" box (Beelink EQ12 with a 512Gb SSD). They don't specify the TBW of the disk but I estimated it quite low from SMART health status. After 3 or 4 months of use, SMART indicates disk reached 15% of its lifetime. With 13.1 TB of Data Units Written (raw value 25,742,265), we can approximate the TBW to around 85 TB, which means the SSD is of a very low quality. This does not bother me because I specifically looked for a low cost, "just enough" box for pfSense.
By comparing SMART measures before and after enabling RAM Disk, I found 3.7/sec vs 0.2 / sec for Data Units Written and 46.2 / sec vs 0.9 / sec for Host Write Commands. I concluded RAM Disk makes a huge difference in my setup. Between RAM Disk and nTopNG, there is no doubt I prefer to keep RAM Disk.

I know what your thinking, Big deal, I got logs in pfSense,

But here the issue is, most often you will be running your AP in bridge mode and having pfSense hand out the DHCP addresses, and if your in bridge mode not much info on whats connecting to the NAS internally behind the firewall is ever seen on the firewall logs. This gives you a level of visibility not normally seen within pfSense unless it is configured. Again if you can do it with one AP you can do it with an alias for many APs on a bigger network. This gives you more information into possibile mac spoofing and unauthorized access. If you use remote access and Dynamic DNS for your network, you can see the firewall logs and the AP logs as well.

same situation for me

@aes4096 said in Error updating repositories:

I solved it using the command certctl rehash

thx. this saved me from setting up everything from scratch.

Initially I tried to view installable packages and wondered as the list was EMPTY.
Then I tried the update process via command line and got multiple errors like:

pkg-static update

pkg-static: An error occured while fetching package Unable to update repository pfSense

pkg-static clean

pkg-static: Repository pfSense-core missing. 'pkg update' required

The trick then was to use the debug option: pkg-static -d update
Here I got an SSL certificate problem: self-signed certificate in certification chain

solved it with your hint above! Thx

@kiokoman Thanks for the reply. This is just buggy app design by the NFL for use on the Roku platform. For now, I will just cast from my iPhone when I want to - that app works without fail. Thanks again.

This breaks connectivity from windows terminal openssh which is at OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 currently in win11.
No one-click way to get that updated.

Also putty 0.62 didn't work but the latest 0.80 does work fine from windows.

Just a heads up.

/Lars

[23.05.1-RELEASE][admin@t]/root: pkg-static upgrade -fy pfSense-repoc
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!
[23.05.1-RELEASE][admin@nst]/root:

I encountered another problem with the upgrade, the upgrade to 2.7.1 or 2.7.2 not offered.
I readed https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html (Repository Metadata Version Errors)
I solved it in this way:

From Diagnostics > Command run command: env ASSUME_ALWAYS_YES=yes pkg-static bootstrap -f
Then Navigate to System > Updates
Set the Branch to Latest Development Snapshots
Wait for the page to refresh
Set the Branch to Latest stable version
And done!
Now im running on 2.7.2

After upgrade The Avaible Packages are displayed.

@jimp thank you for looking into this ticket.

Maybe my certs are to old, we can reproduce this on two different systems.

@mpatzwah said in HAProxy and RDP:

I would like to use for example
rdp1.mydomain.de connect to 172.30.30.101
rdp2.mydomain.de to 172.30.30.102
rdp3.mydomain.de to 172.30.30.103

I guess, all these host names are mapped to a single public IP. Then how do you think, they could be differed in the RDP protocol?

When I switch to Type=tcp rdp works but i can´t use the rule "hosts matches" or "host contains"

Yeah. The host... ACLs target to the host header, which is part of HTTP. Hence it is only available in an HTTP frontend, which is capable to read the header information.

is there any way to get this working ?

You shouldn't do a naked RDP connection over the internet anyway.
So consider to set up a VPN server and go over the VPN, so there is no need use a single IP for multiple RDP servers.

Suddenly "Available Packages" appeared. Nothing changed here.
Miracle???

Just adding my experiences onto this issue. TLDR; can confirm that the proposed method worked for me.

I was seeing not only this issue, but also "Unable to check for updates" in all update-related sections of the Web UI. My update branch was pointing at 2.7.0-RELEASE, but my system was reporting 2.6.0 and the whole system seemed mildly hosed despite still functioning.

After following the recommendations here by pointing the branch to 2.6.0-RELEASE, then connecting via SSH to bootstrap the package system, I had this:

/root: pkg bootstrap -f The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-pfSense_v2_6_0, please wait... Verifying signature with trusted certificate pkg.pfsense.org.20160406... done pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible Installing pkg-1.17.5_4... package pkg is already installed, forced install Extracting pkg-1.17.5_4: 100%

Following that, I tried to run an update via the Web UI, but it said the system is up to date. The branch was now pointing at 2.6.0-DEPRECATED or something like that. I switched the branch back to 2.7.0-RELEASE, and checked for updates via the Web UI again. This time, it looked correct and listed 2.7.0 as an upgrade path. I then carried out a full update. After a nerve-racking 5-minute reboot, pfSense came back online and appears to be operating correctly.