No release versions available, please check subscriptions.

See this post:
https://access.redhat.com/solutions/7001841 yum update subscription-manager Updating Subscription Management repositories. Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 304 B/s | 466 B 00:01 Errors during downloading metadata for repository 'rhel-8-for-x86_64-appstream-rpms': - Status code: 403 for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/appstream/os/repodata/repomd.xml (IP: 23.15.248.251) Error: Failed to download metadata for repo 'rhel-8-for-x86_64-appstream-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried [root@sbidemo yum.repos.d]# subscription-manager release --unset Release preference has been unset [root@sbidemo yum.repos.d]# [root@sbidemo yum.repos.d]# subscription-manager refresh 1 local certificate has been deleted. All local data refreshed [root@sbidemo yum.repos.d]# yum clean all Updating Subscription Management repositories. 78 files removed [root@sbidemo yum.repos.d]# yum update subscription-manager Updating Subscription Management repositories. LocalRepository_BaseOS 3.4 MB/s | 2.4 MB 00:00 LocalRepository_AppStream 6.0 MB/s | 8.1 MB 00:01 MariaDB Server 191 kB/s | 826 kB 00:04 MariaDB MaxScale 1.7 kB/s | 7.0 kB 00:04 MariaDB Tools 2.6 kB/s | 4.3 kB 00:01 MongoDB Repository 59 kB/s | 102 kB 00:01 packages-microsoft-com-prod 5.8 MB/s | 13 MB 00:02 packages-microsoft-com-mssql-server-2019 3.5 MB/s | 5.5 MB 00:01 Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 7.8 MB/s | 68 MB 00:08 Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 7.4 MB/s | 74 MB 00:09 Last metadata expiration check: 0:00:01 ago on Sun 03 Nov 2024 03:23:03 PM +08. Dependencies resolved. ========================================================================================================================================================================================================== Package Architecture Version Repository Size ========================================================================================================================================================================================================== Upgrading: dnf-plugin-subscription-manager x86_64 1.28.42-1.el8 rhel-8-for-x86_64-baseos-rpms 326 k python3-cloud-what x86_64 1.28.42-1.el8 rhel-8-for-x86_64-baseos-rpms 325 k python3-subscription-manager-rhsm x86_64 1.28.42-1.el8 rhel-8-for-x86_64-baseos-rpms 404 k python3-syspurpose x86_64 1.28.42-1.el8 rhel-8-for-x86_64-baseos-rpms 342 k subscription-manager x86_64 1.28.42-1.el8 rhel-8-for-x86_64-baseos-rpms 1.2 M Transaction Summary ========================================================================================================================================================================================================== Upgrade 5 Packages Total download size: 2.5 M Is this ok [y/N]: y Downloading Packages: (1/5): python3-subscription-manager-rhsm-1.28.42-1.el8.x86_64.rpm 848 kB/s | 404 kB 00:00 (2/5): dnf-plugin-subscription-manager-1.28.42-1.el8.x86_64.rpm 545 kB/s | 326 kB 00:00 (3/5): python3-cloud-what-1.28.42-1.el8.x86_64.rpm 444 kB/s | 325 kB 00:00 (4/5): python3-syspurpose-1.28.42-1.el8.x86_64.rpm 966 kB/s | 342 kB 00:00 (5/5): subscription-manager-1.28.42-1.el8.x86_64.rpm 2.7 MB/s | 1.2 MB 00:00 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 2.4 MB/s | 2.5 MB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: python3-cloud-what-1.28.42-1.el8.x86_64 1/1 Upgrading : python3-cloud-what-1.28.42-1.el8.x86_64 1/10 Upgrading : python3-subscription-manager-rhsm-1.28.42-1.el8.x86_64 2/10 Upgrading : python3-syspurpose-1.28.42-1.el8.x86_64 3/10 Upgrading : dnf-plugin-subscription-manager-1.28.42-1.el8.x86_64 4/10 Running scriptlet: subscription-manager-1.28.42-1.el8.x86_64 5/10 Upgrading : subscription-manager-1.28.42-1.el8.x86_64 5/10 Running scriptlet: subscription-manager-1.28.42-1.el8.x86_64 5/10 Running scriptlet: subscription-manager-1.28.36-2.el8.x86_64 6/10 Cleanup : subscription-manager-1.28.36-2.el8.x86_64 6/10 Running scriptlet: subscription-manager-1.28.36-2.el8.x86_64 6/10 Cleanup : python3-syspurpose-1.28.36-2.el8.x86_64 7/10 Cleanup : python3-subscription-manager-rhsm-1.28.36-2.el8.x86_64 8/10 Cleanup : python3-cloud-what-1.28.36-2.el8.x86_64 9/10 Cleanup : dnf-plugin-subscription-manager-1.28.36-2.el8.x86_64 10/10 Running scriptlet: dnf-plugin-subscription-manager-1.28.36-2.el8.x86_64 10/10 /sbin/ldconfig: /lib64/libmaodbc.so is not a symbolic link Verifying : dnf-plugin-subscription-manager-1.28.42-1.el8.x86_64 1/10 Verifying : dnf-plugin-subscription-manager-1.28.36-2.el8.x86_64 2/10 Verifying : python3-cloud-what-1.28.42-1.el8.x86_64 3/10 Verifying : python3-cloud-what-1.28.36-2.el8.x86_64 4/10 Verifying : python3-subscription-manager-rhsm-1.28.42-1.el8.x86_64 5/10 Verifying : python3-subscription-manager-rhsm-1.28.36-2.el8.x86_64 6/10 Verifying : python3-syspurpose-1.28.42-1.el8.x86_64 7/10 Verifying : python3-syspurpose-1.28.36-2.el8.x86_64 8/10 Verifying : subscription-manager-1.28.42-1.el8.x86_64 9/10 Verifying : subscription-manager-1.28.36-2.el8.x86_64 10/10 Installed products updated. Upgraded: dnf-plugin-subscription-manager-1.28.42-1.el8.x86_64 python3-cloud-what-1.28.42-1.el8.x86_64 python3-subscription-manager-rhsm-1.28.42-1.el8.x86_64 python3-syspurpose-1.28.42-1.el8.x86_64 subscription-manager-1.28.42-1.el8.x86_64 Complete! [root@sbidemo yum.repos.d]# subscription-manager release --set=8.4 Release set to: 8.4 [root@sbidemo yum.repos.d]# subscription-manager refresh All local data refreshed [root@sbidemo yum.repos.d]# yum clean all Updating Subscription Management repositories. 62 files removed [root@sbidemo yum.repos.d]# subscription-manager repos --enable=rhel-8-for-x86_64-baseos-e4s-rpms \ > --enable=rhel-8-for-x86_64-appstream-e4s-rpms Repository 'rhel-8-for-x86_64-baseos-e4s-rpms' is enabled for this system. Repository 'rhel-8-for-x86_64-appstream-e4s-rpms' is enabled for this system

Rear carbon nards

Identifying missing libraries

file /usr/lib64/libmaodbc.so /usr/lib64/libmaodbc.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=46b88e88537040b046508adabf838a57b5feefe2, with debug_info, not stripped ldd /usr/lib64/libmaodbc.so linux-vdso.so.1 (0x00007ffd2c7f9000) libodbcinst.so.2 => /lib64/libodbcinst.so.2 (0x00007f043ae00000) libm.so.6 => /lib64/libm.so.6 (0x00007f043b125000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f043b52b000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f043b526000) libssl.so.10 => not found libcrypto.so.10 => not found libc.so.6 => /lib64/libc.so.6 (0x00007f043aa00000) libltdl.so.7 => /lib64/libltdl.so.7 (0x00007f043b518000) librt.so.1 => /lib64/librt.so.1 (0x00007f043b513000) /lib64/ld-linux-x86-64.so.2 (0x00007f043b53e000)

Migrate Env

Backup: /home/unica /apps /var/lib/mysql Backup SQLServer using sqlcmd Install OS with matching filesystem (350GB disk) Install: mariadb sqlserver Shutdown mariadb, sqlserver Restore: /home/unica /apps /var/lib/mysql Restore sqlserver using sqlcmd Copy: /etc/odbc.ini Update OCBC driver https://dlm.mariadb.com/2454043/Connectors/odbc/connector-odbc-3.1.17/mariadb-connector-odbc-3.1.17-rhel9-amd64.tar.gz

yum install: Error: Unable to find a match

If you get the error "Error: Unable to find a match" when running a yum install, do a "yum repolist" to see if the repo exists.
if it exists, maybe you updated the repo and need to a clean: yum clean all Updating Subscription Management repositories. 44 files removed After that try to do a yum install again.

Unable to establish IPMI v2 / RMCP+ session

See this post:

https://stackoverflow.com/questions/51948745/error-unable-to-establish-ipmi-v2-rmcp-session 13 I installed the ipmitool 1.8.18 in the CentOS7.2 Dedicated Server, I can use it for check self own ipmi data: # ipmitool -I open power status Chassis Power is on but I want to check other ipmi address' status, I will get this error: # ipmitool -H 172.16.22.237 -U root -P mypassword -I lanplus chassis status -v Get Auth Capabilities error Error issuing Get Channel Authentication Capabilities request Error: Unable to establish IPMI v2 / RMCP+ session in the being controlled Server I use ipmitool checked the lan: [root@localhost ~]# ipmitool -I open lan print 1 Set in Progress : Set Complete Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable : Callback : MD2 MD5 PASSWORD : User : MD2 MD5 PASSWORD : Operator : MD2 MD5 PASSWORD : Admin : MD2 MD5 PASSWORD : OEM : MD2 MD5 PASSWORD IP Address Source : Static Address IP Address : 172.16.22.237 Subnet Mask : 255.255.255.0 MAC Address : 00:25:90:a9:42:4a SNMP Community String : public IP Header : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Default Gateway IP : 0.0.0.0 Default Gateway MAC : 00:00:00:00:00:00 Backup Gateway IP : 0.0.0.0 Backup Gateway MAC : 00:00:00:00:00:00 802.1q VLAN ID : Disabled 802.1q VLAN Priority : 0 RMCP+ Cipher Suites : 1,2,3,6,7,8,11,12 Cipher Suite Priv Max : aaaaXXaaaXXaaXX : X=Cipher Suite Unused : c=CALLBACK : u=USER : o=OPERATOR : a=ADMIN : O=OEM Bad Password Threshold : Not Available EDIT-01 I use nmap get bellow information: # nmap -p 623 -sU -P0 172.16.22.237 Starting Nmap 6.40 ( http://nmap.org ) at 2018-08-22 08:01 CST Nmap scan report for 172.16.22.237 Host is up. PORT STATE SERVICE 623/udp open|filtered asf-rmcp Nmap done: 1 IP address (1 host up) scanned in 2.11 seconds ipmiipmitool Share Improve this question Follow edited Aug 22, 2018 at 8:01 asked Aug 21, 2018 at 12:31 aircraft's user avatar aircraft 26.7k2828 gold badges101101 silver badges173173 bronze badges This seems to be an authentication error. Please take note that RMCP+ supports in addition to various authentication extensions, encryption of data transmission. – U880D CommentedAug 22, 2018 at 7:28 I also tried the -I lan. – aircraft CommentedAug 22, 2018 at 7:32 @U880D See my edited post, bro. – aircraft CommentedAug 22, 2018 at 7:42 @U880D When I use the -H 172.16.22.237 -U root -P mypassword , the password is the origin password, without encryption. does this is the reason? – aircraft CommentedAug 22, 2018 at 7:46 1 -U admin and you must know the correct admin password. Once you are sure of those, you need to try -C0 to -C3 for different cipher suites, as it says "Cipher Suite Priv Max : aaaaXXaaaXXaaXX". – Gambit Support CommentedAug 22, 2018 at 12:29 Show 5 more comments 9 Answers Sorted by: Highest score (default) 9 (SOLVED for a Dell machine) I had exactly the same issue on a Dell Poweredge R430 machine after having changed the system motherboard: although my credentials were restored in the new IDRAC board from the chassis flash backup, and despite the fact my credentials still allowed me to enter the IDRAC Web Interface, I was not able anymore to interact with the IDRAC board through IPMIv2/lanplus/SOL interface, facing the same problem of Error: Unable to establish IPMI v2 / RMCP+ session. For me the solution was, as suggested by Rupeshrams herein https://stackoverflow.com/a/55615668/13646401, to "reset ipmi default password to the same old one" ("same" because I had system tools all hardcoded with old credentials) with the IDRAC Web Interface as this : In your browser, enter the (static) ip address of the IDRAC : this should open an https web site. Then : Menu Overview -> IDRAC SETTINGS -> User Authentication -> Click on the userID of your admin account -> Next -> check "change your password" checkbox and enter the same (or new) password -> Apply Why : I understood that passwords were hashed/encrypted in my previous motherboard with a key specific to that old motherboard. By Changing the motherboard, and restoring a user database hashed by a from-now-on unknown key, my credentials became invalid, at least for using ipmitool and IPMIv2 interface. What was confusing me, but that finally helped me to solve the problem, was the fact that old credentials were still valid to enter the IDRAC web interface. TIP: every advice to check for IPMIv2/UDP 623 service availability with nmap or to "activate SOL (Serial Over Lan)" are helpful: "SOL activate" can be easily performed on the IDRAC web interface: Menu Overview -> IDRAC SETTINGS -> Network -> SerialOverLAN

Dell R710 Gen II Motherboard

Dell manufactured two generations of the PowerEdge R710 server model and therefore two different revisions of the PowerEdge R710 system board. It is important to understand the differences between the system boards prior to upgrading or replacing system components. All system boards support either PC3-8500 (1066MHz) or PC3-10600 (1333MHz) DDR3 memory DIMMS. All system boards feature eighteen (18) slots; nine (9) for each processor and will accommodate up for a maximum of 288GB of RAM. Generation I system boards (motherboards) support Intel Xeon 5500/5600 series dual and quad-core processors up to 95W. They will NOT work with any of the quad or six-core 130W CPUs in the Intel Xeon X5600 series. Part numbers for generation I system boards include YDJK3, N047H, 7THW3, VWN1R and 0W9X3. Generation II system boards added support for Intel Xeon X5600 series 130W processors such as the X5680 and X5690 CPUs. If the front of your PowerEdge R710 has a Roman numeral "II", it likely has a generation II system board. Part numbers for generation II system boards include XDX06, 0NH4P and YMXG9. TipIf you're replacing a generation I system board in your PowerEdge R710, consider upgrading to a generation II. Doing so now will allow you to install faster CPUs in the future, thereby adding more processing power and extending the life of your system.

https://store.flagshiptech.com/system-boards-motherboards-12/#:~:text=If%20the%20front%20of%20your,include%20XDX06%2C%200NH4P%20and%20YMXG9.

Using putty to connect to AWS EC2

https://asf.alaska.edu/how-to/data-recipes/connect-to-your-ec2-instance-using-putty-v1-1/

can see this also:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-from-windows.html

Install Docker on Oracle Linux 8

https://collabnix.com/how-to-install-docker-on-oracle-linux-a-step-by-step-guide/

Use domain instead of IP for Prestashop

Fixed mine at least, with a little help I found that if you scroll far enough down on the SEO & URL's Page within the Backend>Preferences Section there is a URL's bit where you can punch in the domain name you want to use instead of the IP Address.

Install docker-compose on RHEL 9

sudo curl -L "https://github.com/docker/compose/releases/download/1.23.2/docker-compose-$(uname -s)-$(uname -m)" -o docker-compose
sudo mv docker-compose /usr/local/bin && sudo chmod +x /usr/local/bin/docker-compose
sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose

Install Docker on RHEL9.4

Source:https://gopesh3652.medium.com/installing-docker-in-rhel-9-locally-by-configuring-yum-42bdfea103f0 Introduction Docker is a popular containerization platform that simplifies the process of building, distributing, and running applications inside containers. Red Hat Enterprise Linux (RHEL) 9 is a stable and reliable operating system widely used in production environments. In this guide, we’ll walk you through the step-by-step process of installing Docker on RHEL 9 by configuring the YUM package manager. Prerequisites Before proceeding with the installation, ensure you have the following: A machine running Red Hat Enterprise Linux 9. Administrative access to the system. An active internet connection. Step 1: Update the System The first step is to ensure your system is up-to-date. Open a terminal and execute the following command: sudo yum update Step 2: Add Docker Repository to YUM To install Docker on RHEL 9, you’ll need to add the Docker repository to the YUM configuration. Create a new file named “docker.repo” in the “/etc/yum.repos.d/” directory using a text editor like vi or nano: sudo vi /etc/yum.repos.d/docker.repo Add the following lines to the file: [docker-ce-stable] name=Docker CE Stable - $basearch baseurl=https://download.docker.com/linux/rhel/9/$basearch/stable enabled=1 gpgcheck=1 gpgkey=https://download.docker.com/linux/rhel/gpg Save the file and exit the text editor. Step 3: Install Docker Now that you’ve added the Docker repository, you can install Docker using the YUM package manager: sudo yum install docker-ce --nobest Step 4: Start and Enable Docker After the installation is complete, start the Docker service and enable it to start on boot: sudo systemctl start docker sudo systemctl enable docker Step 5: Verify Docker Installation To verify that Docker is installed correctly, run the following command: docker --version This command will display the installed Docker version, confirming that the installation was successful. Step 6: Test Docker with a Simple Container To ensure Docker is functioning properly, test it with a simple container: sudo docker run hello-world Docker will download the “hello-world” image and run a container from it. If everything is set up correctly, you’ll see a message indicating a successful installation Remember that Docker requires root privileges to run, so use the “sudo” command when interacting with Docker unless you’ve granted your user non-root access to Docker.

RHEL 9.4 goes to emergency mode

This was my life saver: https://kb.synology.com/en-me/DSM/tutorial/My_virtual_machine_running_RHEL_9_enters_emergency_mode Diagnosis In RHEL 9.0, the use_devicesfile option in Logical Volume Manager (LVM) is enabled by default, checking whether the Physical Volume Identifier (PVID) of the LVM volume is identical to the last time the virtual machine was running. When it is not identical, the virtual machine may enter emergency mode. However, the following operations will result in different PVIDs: Change the virtual disk controller from VirtIO SCSI to IDE or SATA. Clone a virtual machine with VirtIO SCSI controller. Import a virtual machine with VirtIO SCSI controller which was exported previously. Therefore, after the operations above, your virtual machine may enter emergency mode. Resolution Recover the virtual machine from the emergency mode In emergency mode, enter the root password of the virtual machine. Enter the command below to delete the original device file. [root@localhost ~]# rm /etc/lvm/devices/system.devices Enter the command below to create a new device file. [root@localhost ~]# vgimportdevices -a Enter the command below to reboot the virtual machine. [root@localhost ~]# reboot Prevent the virtual machine from entering emergency mode Open the configuration file /etc/lvm/lvm.conf. Locate the use_devicesfile option. # use_devicesfile = 0 Uncomment the option and make sure it is set to 0. use_devicesfile = 0

How to setup Telegram BOT for notifications

Assume the bot name is my_bot. 1- Add the bot to the group. Go to the group, click on group name, click on Add members, in the searchbox search for your bot like this: @my_bot, select your bot and click add. 2- Send a dummy message to the bot. You can use this example: /my_id @my_bot (I tried a few messages, not all the messages work. The example above works fine. Maybe the message should start with /) 3- Go to following url: https://api.telegram.org/botXXX:YYYY/getUpdates replace XXX:YYYY with your bot token 4- Look for "chat":{"id":-zzzzzzzzzz, -zzzzzzzzzz is your chat id (with the negative sign). 5- Testing: You can test sending a message to the group with a curl: curl -X POST "https://api.telegram.org/botXXX:YYYY/sendMessage" -d "chat_id=-zzzzzzzzzz&text=my sample text" If you miss step 2, there would be no update for the group you are looking for. Also if there are multiple groups, you can look for the group name in the response ("title":"group_name").



You can get a token from https://t.me/BotFather. In order to get the group chat id, do as follows: Add the Telegram BOT to the group. Get the list of updates for your BOT: https://api.telegram.org/bot/getUpdates Ex: https://api.telegram.org/bot123456789:jbd78sadvbdy63d37gda37bd8/getUpdates Look for the "chat" object: { "update_id": 8393, "message": { "message_id": 3, "from": { "id": 7474, "first_name": "AAA" }, "chat": { "id": , "title": "" }, "date": 25497, "new_chat_participant": { "id": 71, "first_name": "NAME", "username": "YOUR_BOT_NAME" } } } This is a sample of the response when you add your BOT into a group. Use the "id" of the "chat" object to send your messages. (If you created the new group with the bot and you only get {"ok":true,"result":[]}, remove and add the bot again to the group) Private chart only works in image argoprojlabs/argocd-notifications:v1.1.0 or above.

How to install Dockers and UptimeKuma on Debian

Follow this for the docker: https://gcore.com/learning/how-to-install-docker-engine-debian/ And just the UptimeKuma section: https://xtom.com/blog/how-to-setup-uptime-kuma/

ssh keys with redhat

How to use ssh keys with putty and Red Hat Enterprise Linux ? Solution Verified - Updated August 6 2024 at 5:40 AM - English Environment Red Hat Enterprise Linux (RHEL) 6.3 Issue SSH Keys generated by Putty do not work with openssh in Red Hat Enterprise Linux Resolution To make it working convert the keys generated by Open-ssh to putty's format: First generate keys on RHEL: Raw # ssh-keygen -t rsa Then put public key into authorized_keys file: Raw # cat public_key >> ~/.ssh/authorized_keys Set proper permissions: Raw # chmod 700 ~/.ssh # chmod 600 ~/.ssh/authorized_keys Copy (for example with Winscp) private key into Windows machine. Start the program called "puttygen", select "conversion" --> "Import keys" --> "your_private_key". Save it somewhere in putty format. Note: In order to use the converted key please create new putty session and fill the following fields: "auto-login username" (username you wish to use as login) . "connection" --> "ssh" --> "auth" --> "browse" (here please point to your newly generated putty key)--> "session" --> "save". Root Cause

Cannot access services through WAN IP from internal network

See this post: https://forum.netgate.com/topic/114507/cannot-access-services-through-wan-ip-from-internal-network/8 Basically need to turn on NAT Reflection on PFSENSE. In the NAT Rule, "NAT reflection" set to: "Enable (NAT+Proxy)" If you put Pure NAT, local LAN will (same IP segment) will not be able to access.

Generate AWS Key for ACME Cert

Use CLI command shell option

https://www.youtube.com/watch?v=cB6oKJjr4Ls

Wordpress Dockers on TrueNAS

If you used hostPath, you should make sure the user and group id 33 have r/w access to the host paths you defined. (www-data) https://github.com/truenas/charts/issues/2665

HAProxy with SSL

See this post:https://www.reddit.com/r/selfhosted/comments/16sq2fa/anyone_get_firefly3_to_work_behind_pfsense_haproxy/ This probably isn't the most helpful, but I was successfully able to get Firefly 3 working behind the reverse proxy caddy. I didn't have to rewrite any headers. I only had to set TRUSTED_PROXIES=** as you said you did. (for firefly) Solved. I was able to find a solution in this article: https://discourse.haproxy.org/t/mixed-content-warning-when-using-https/981/9 Specifically, I added "http-response set-header Content-Security-Policy upgrade-insecure-requests" to the "backend pass thru" section for the HAProxy backend server. I believe, if I understand this correctly, it forces HAProxy to scan all page content and replace insecure link references that the page may contain

Nextcloud and OnlyOffice and Collabora

https://forums.truenas.com/t/nextcloud-and-onlyoffice-integration/1172 https://forums.truenas.com/t/nextcloud-and-collabora-integration/1173

Recommended Memory Configurations for Dell R710 - 128GB with 16GB stick

R710 Upgrade options

https://www.greenpcgamers.com/dell/dell-poweredge-rack/poweredge-11th-gen-servers/poweredge-r710-hardware-upgrade-guide-greenpcgamers-com/ Recommended Processors: *You must have a Gen II System Board to install 130W CPU’s* Up to 2 x QC Xeon X5667 3.06Ghz 12MB 6.40GTs 95W Processors | 3.46 Max Turbo Frequency (SLBVA) Up to 2 x QC Xeon X5677 3.46Ghz 12MB 6.40GTs 130W Processors | 3.73 Max Turbo Frequency (SLBV9) Up to 2 x QC Xeon X5687 3.6Ghz 12MB 6.40GTs 130W Processors | 3.86Ghz Max Turbo Frequency (SLBVY) Up to 2 x 6C Xeon X5675 3.06Ghz 12MB 6.40GTs 95W Processors | 3.46Ghz Max Turbo Frequency (SLBYL) Up to 2 x 6C Xeon X5680 3.33Ghz 12MB 6.40GTs 130W Processors | 3.60Ghz Max Turbo Frequency (SLBV5) Up to 2 x 6C Xeon X5690 3.46Ghz 12MB 6.40GTs 130W Processors | 3.73Ghz Max Turbo Frequency (SLBVX) Memory PNs: 2GB PC10600R 1Rx8 ECC Reg (093VH) 2GB PC10600R 2Rx8 ECC Reg (DP143) 4GB PC10600R 2Rx4 ECC Reg Shielded (NN876) 4GB PC10600R 2Rx8 ECC Reg (7H8J8) 4GB PC10600R 2Rx8 PC3L ECC Reg (9J5WF or H5DDH) 8GB PC10600R 2Rx4 PC3L ECC Reg (P9RN2) 8GB PC10600R 2Rx4 ECC Reg Shielded (X3R5M) 16GB PC10600R 2Rx4 PC3L ECC Reg (MGY5T) *You will need to install 2 processors to use all 18 memory slots* 4 x 8GB PC10600R ECC Reg Modules (32GB) 6 x 8GB PC10600R ECC Reg Modules (48GB) 8 x 8GB PC10600 ECC Reg Modules (64GB) 8 x 16GB PC10600R ECC Reg Modules (128GB) 12 x 16GB PC10600R ECC Reg Modules (192GB) 16 x 16GB PC10600R ECC Reg Modules (256GB) 18 x 16GB PC10600R ECC Reg Modules (288GB)

Upgraded my R710 to X5675

I bought the x5690 but it could not boot :-( wasted $70. I bought the x5675 at $60 and it is working fine. The difference between the Gen 1 and Gen 2 R710 is the CPU TDP rating it can support. The Gen1 will not support processors with a 130W TDP whilst the Gen2 will. Basically anything higher than the X5675 (X5677, X5680, X5688, X5690) is not supported on the Gen 1. The Gen 1 will support Westmere providing your BIOS is of a new enough version to support (which if it had E5620’s, then it is).

Nextcloud on TrueNas Scale with haproxy

this saved me :https://www.truenas.com/community/threads/nextcloud-redirects-to-local-ip-when-trying-to-access-from-domain.99649/#post-757130 1 Apr 23, 2023 #12 for anyone still trying to make it work with official app. I solve it by adding Nextcloud environment variables (one of 2 showed fixed it) instead of editing config.php. I ataching picture with my working conf. In case if picture wont work: Add Nextcloud enviroment in app setup or edit existing app. Name: OVERWRITEHOST and/or OVERWRITECLIURL Value: cloud.yourdomain.com