Tag: SysAdmin

💚 Hosting that works hard, treads lightly.   Big news: Heart Internet is now officially listed with the Green Web Foundation. That means our hosting services are recognised as being powered by 100% renewable energy – wind, solar, and hydro, all thanks to our partnership with EDF. So while your website might be generating traffic, [read more...]

Without web hosting, your website would not be visible or accessible to users! It is crucial to host your website with a website hosting service to ensure that your business has an online presence. Web hosts will securely store your website’s files, images, and digital content on a server, making it accessible to the public [read more...]

If you get one of the following messages from the Plesk migrator you should check that you are using root as the username along with the Plesk admin password. “The source server does not appear to be a Plesk server” “Plesk Migrator tool requires original ‘root’ user access or root user with GUI/UID = 0.” [read more...]

If you get one of the following messages from the Plesk migrator you should check that you are using root as the username along with the Plesk admin password. “The source server does not appear to be a Plesk server” “Plesk Migrator tool requires original ‘root’ user access or root user with GUI/UID = 0.” [read more...]

Did you know that the fonts you use on your website can impact the way your customers perceive and interact with your brand?

Black Friday is here, and we’re bringing you incredible savings to help your business thrive online. From 29th November 2024 to 9th December 2024, you can enjoy 15% off some of our most popular products to get the tools you need at a fraction of the cost. What’s on Offer? Here’s what you can save [read more...]

A slow website is like a slow waiter: it doesn’t matter how good the food is if the service is frustratingly sluggish. If your site takes too long to load, visitors are likely to abandon it faster than you can say “bounce rate.” But fear not! Here are some tips to help you optimise your [read more...]

You can now get up to 33% off the price of a cPanel-managed Web Hosting plan at Heart Internet.

Including options for optimising your cart, boosting customer loyalty, and selling tickets.

Discover the appeal of .ninja, .coffee, .guru and more - all available in our domain name sale.

Is it possible to display Active directory user attribute based information to desktop by bginfo using domain group policies? If possible how? For example: I want to display active directory custom user attributes 'Main manager and Assistant manger' name on users desktop.

I spanned some (3) disks together as a temporary measure in windows 10 meaning to copy all the data over to a 6 disk raid for safety's sake, To make a sad story short , I never got around to getting the copy done and windows June update did SOMETHING to destroy the volume. After the update upon the (first) boot(s) windows would stall at the swirling circle and one of the disks in the spanned set would be at 100% usage for hours . I finally just shut the system down and have been trying to get the disks back together since. This is all part of moving to a new MOBO weeks ago (hence the temp spanned). This volume basically has about 20 years of documents,programs, taxes, etc. not to mention downloads and software from years gone by. I should mention it was just fine until rebooting from the update. I move those disk over to the old mother board with the pre-update windows installed on it from a cloned disk (in case the move went badly moving to ssd ) not connected to the inter

After fresh kubespray install my worker node has calico pod in Init:CrashLoopBackOff state. (We have deployed cluster this way before - a few months ago and all was good) Error log from journalctl: calico/node is not ready: bird/confd is not live: exit status 1 "ExecSync cmd from runtime service failed" err="rpc error: code = Unknown desc = failed to exec in container: container is in CONTAINER_EXITED state" containerID="242810527b0b21f9d69bf29691ed958a63b12d87d0fa470733e1f0c378787890" cmd=["/bin/calico-node","-felix-live","-bird-live"] Have spent so much time looking how to resolve it...No luck. (Saw identical issues, nothing helped) Have redeployed cluster, added/remove new node, nothing helped. In pod events, I see the following: Liveness probe failed: calico/node is not ready: Felix is not live: Get "http://localhost:9099/liveness": dial tcp 127.0.0.1:9099: connect: connection refused

I have been trying to configure NetworkManager to work with both DHCP and Link-Local addresses when no DHCP is available. At first the link-local addresses are created. But when the DHCP fails to obtain a lease, the link-local addresses get removed. This continues, looping, addresses appear, work for a while and are then removed. I enabled debugging for NetworkManager, here is the pertinent section: 42.8350] dhcp4 (eth0): canceled DHCP transaction 42.8351] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) 42.8352] dhcp4 (eth0): state changed no lease 42.8357] device[d5b7e257c4672089] (eth0): ip:ll4: set state none (was done) 42.8358] device[d5b7e257c4672089] (eth0): ip:manual4: set state none 42.8358] device[d5b7e257c4672089] (eth0): ip:manual6: set state none 42.8359] device[d5b7e257c4672089] (eth0): ip: set (combined) state none (was fail, reason: ip-state-clear) 42.8360] ndisc[0x559e947140,"eth0"]: stopping neig

I could use your help with this, I've got an issue with the RAID5 array in my server, where I'm getting seemingly random DeviceDisappeared and NewArray events (always in the same second) from mdadm (sometimes followed by a rebuild). I've gathered as much information I think might be relevant as possible, and am wondering if you have any suggestions on what I can try/investigate next to fix/prevent this. Please let me know if there's any other debug information that might be helpful. Any insight would be appreciated. Symptoms Small selection of journalctl --since "1 week ago" | grep mdadm: Jun 11 06:24:11 homeserver sh[2036476]: mdadm: DeviceDisappeared event detected on md device /dev/md/md0 Jun 11 06:24:11 homeserver sh[2036476]: mdadm: NewArray event detected on md device /dev/md0 Jun 11 06:24:26 homeserver mdadm[2041255]: mdadm: DeviceDisappeared event detected on md device /dev/md/md0 J

HTTP3 uses QUIC. QUIQ is UDP. Does this mean all router firewall rules for port 80 and 443 must be changed from TCP to UDP?

I am trying to get a user's systemd services to start automatically upon boot in an enterprise where users' home directories are auto-mounted by autofs. The user has a service unit in ~/.config/systemd/user/, it is wanted by their default.target, and I have enabled linger for the user. However, while their service auto-starts upon boot on some systems, on other systems it does not. Looking at the order of the journal events during boot, I believe I see the problem: On the systems where this is not working, systemd-user-sessions.service is starting before autofs.service. So the user's home directory is not mounted at the point when the user-specific service manager would be looking there for systemd units & config. I realize I could fix this by customizing systemd-user-sessions.service to add After=autofs.service, or similarly by customizing autofs.service to add

UPC APC Smart-UPS SMT1000 Windows server 2022 Standard Powerchute version 1.3.0.301 Usb cable is used to connect the UPC to the server. The script I wrote to power off my server using "PowerChute Serial Shutdown" is executed up to the second line, skips the third and continues from the fourth (according to C:\Program Files\APC\PowerChute Serial Shutdown\agent\cmdfile.log). This is the third line of the script: @start "ssh windows", "C:\Windows\System32\OpenSSH"\ssh.exe -i %DIR_KEY%\keyshutdownVM admin@%IPADDR% This line connects to a virtual machine, shutdown several databases and power off the virtual machine. Things that I tried: Update the firmware of the UPS. Be sure the script can be executed from command prompt without problems. Change the usb cable used to connect the UPS to the server. ¿Would you help to figure out what is th

I am deploying Dovecot FTS with Solr backend for full-text search on my mail server (Dovecot 2.3.x, Solr 9.x). For performance and storage reasons, I want only a subset of my mail accounts (for example, only a few specific users, or a whole domain) to have their mails indexed in Solr and to benefit from server-side full-text search. I do not want the FTS plugin to index every single account or mailbox on my system. My questions: Is it possible to configure Dovecot FTS (with Solr backend) to only index certain users or domains, and not the whole server? If so, how can this be achieved? Is there a per-user or per-domain configuration, or a way to conditionally load the fts and fts_solr plugins only for certain accounts? Any pointers, example configurations, or references to the documentation are very welcome!

I have a docker stack consisting of caddy and wordpress currently in development at https://localhost and I am getting two critical erros: I am not sure what could be causing this The REST API encountered an error Performance The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages. When testing the REST API, an error was encountered: REST API Endpoint: https://localhost/wp-json/wp/v2/types/post?context=edit REST API Response: (http_request_failed) cURL error 7: Failed to connect to localhost port 443 after 0 ms: Couldn't connect to server and Your site could not complete a loopback request Performance Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability. The loopback