Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Tad Bittoomuch

  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About Tad Bittoomuch

  • Title
  • Birthday July 31

Profile Information

  • Location

Recent Profile Visitors

360 profile views
  1. Did you experience the motherboard not detecting the CPU in this configuration? Having the IHS held in place by the socket should be fine for normal operation, but I'd be interested to see if you start seeing the error after a few days. My other questions are: Is there an error message when the CPU is not detected, i.e. what happens on the display? Does this occur when logged into Windows or is it only when you turn on the computer?
  2. Was your motherboard exhibiting this behaviour after switching to the 4790k but before you delidded it? It's a rather odd that you you progressed straight to delidding after discovering that the temperatures are a bit high - I would have looked for a potential different cause, such as improperly positioned/wrong mounting pressure of the waterblock, or a defective or blocked/obstructed loop or pump. The 4790k itself is a rather hot CPU. I used to have one and had a 240mm AIO and temps would reach mid to high 70s/low 80s under sustained load. You probably know this, but this is what the 4790k looks like when delidded: There are two rows of resistors next to the die - I am wondering if, during the process of delidding you accidentally managed to slice one or two of them off. This could be causing your CPU to not be detected by your motherboard (Is there an error message?). The other possible cause could be that there's too little or too much pressure on the die itself. This is why delidding your CPU voids the warranty, because the silicon adhesive that attaches the heatspreader to the substrate contributes a non-zero value to the CPU package thickness. It's possible that the slight change in CPU thickness contributed to the errors you are experiencing with your motherboard. I'd suggest removing the silicon adhesive and simply resting the IHS on top of the substrate, then closing the retention bracket while the PC is horizontal. Try reseating the waterblock and maybe investigate any possible blockages in your cooling loop. Hope that helps
  3. It depends on your CPU, and what software you are using to read the temperatures. Some programs can't read the temperature sensor on specific CPU architectures correctly. If your CPU is Intel, use Intel Extreme Tuning Utility or HWiNFO or to read the temperature. If your CPU is AMD Ryzen, use Ryzen Master. If your CPU is AMD pre-Ryzen, I'd suggest AMD Overdrive because of the way the FX CPUs and A Series APUs report their operating temperatures. If you're interested, here's a reddit thread that goes into more detail.
  4. Sending a desktop computer in the post makes me a little uncomfortable (asking for trouble), but I don't think that's the problem here. Did your girlfriend try different powerpoints when testing all the parts together? Is she using a powerboard and/or UPS? Has she tested all the combinations of DIMMs to memory slots? (i.e. DIMM #1 in slot 1 & 2 and DIMM #2 in slot 1 & 2) Replugging all power supply cables? Reseating CPU & cooler? GPU in different PCIe slots? Making sure the PCIe power connectors are not connected to the CPU EPS connectors and vice versa? Other than that I can't understand why a computer would function differently depending on it's physical location. The only different variable I can think of is power supply related and quality of power delivered. Hope you find this useful and manage to work out what the problem is :)
  5. When you enable it in the BIOS, does virtualisation stay enabled or does it revert to disabled after a reboot? Did you build your computer yourself, or did you buy it from a shop/online second hand? What model is it/what company manufactures the motherboard? What CPU do you have (does it support virtualisation)? It could be ex-enterprise, as companies upgrade all their IT equipment en-masse every 3-5 years which floods the used hardware market. If it's a company's ex-asset, the BIOS may be password protected, and will only allow you to read the settings but not write changes. Some BIOSes in read-only password protected mode will allow you to change settings, but those settings will not persist after a reboot. Fortunately, there is a fix - you can clear the CMOS by removing the small battery located on the motherboard. Wait 10-20 seconds, and then replace the battery. The password on the BIOS will have been removed and you should be able to enable virtualisation.
  6. Generally, unnecessarily having exposed ports poses a potential security risk. I had a brief look at Storage Spaces in Windows 10 and from what I can deduce, I think you've created a storage pool and then shared the drive over your local network. What I'd recommend is to use a L2TP VPN tunnel to access your local network. Then you'll be able to access any local network hosts as if you're physically connected to them. You could use a PPTP VPN tunnel but they're obsoleted by L2TP and have known security issues. Once you tunnel into your local network, your network drive should connect automatically. If you don't want to do this, you can port forward the specific Windows SMB ports for network drives in your access point: NB-Name 137/UDP NB-Datagram 138/UDP NB-Session 139/TCP SMB 445/TCP Make sure these ports are allowed in Windows Firewall as well. Hopefully this is helpful
  7. I ended up doing this with a bit of additional CSS. The theme (Storefront) isn't customisable enough to do this natively. The background image is added: .site-content { background-image: url("I don't know, some image or something.tiff"); background-size: cover; } EDIT: If you want the image to tile itself vertically, change the value of background-size to '100% auto' and add 'background-repeat: repeat-y;' to the next line. .site-content { background-image: url("I don't know, some image or something.tiff"); background-size: 100% auto; background-repeat: repeat-y; } Add a solid colour background behind page content as well as remove some utterly senseless, fundamentally flawed padding: #content > div { background-color: #c4c4c4; padding-top: 2em; } And finally, remove some more inane padding on the elements that shouldn't have been in the theme in the first place: .home.blog .site-header, .home.page:not(.page-template-template-homepage) .site-header, .home.post-type-archive-product .site-header { margin-bottom: 0; } Honestly, if I wasn't making the website for somebody else, I wouldn't be using WordPress... It's so aggravating to have to peel back these layers of thoughtless design.
  8. I just tried that, except the images aren't continuous - unless I'm doing something wrong. What I really need is a way to add a background image, but leave the middle a solid colour so the content is readable but also scales to the screen size.
  9. Hi everyone, Is there a way (in Wordpress 5.3.2) to add a background image to a site that doesn't obscure the content? Kind of like this ↓ Left is what I currently have, right is what I want. In the WP admin panel, I have tried Appearance → Background → Choose Image but that puts the content in front of the entire image and I don't want that. I also don't want to edit the image to include a blank section in the middle for content, as I want to have the site be usable on multiple screen sizes without looking amateur. The image I have in mind will be able to seamlessly tessellate, and because I'm building a shop for a friend, it needs to work regardless of how long the page is/scroll with the content. I tried googling something along the lines of 'wordpress image sidebar' but that returns results where images are in the sidebar widget, and I also don't want that. If anyone has any experience with Wordpress and wouldn't mind sharing some expertise, that'd be really, really appreciated Alternatively if there's a plugin that can do this, brilliant - I'll give it a look. Thanks
  10. Ok, this makes sense. I changed the port forwards to now be directed to the proxy server. Just one question though - for all the mail ports (143, 995, 25, 110, 993 and 465) should I have a separate server block in the proxy config for each port or will a catch-all block like the one below take all traffic regardless of port and throw it onto the mail server? Catch-all server block (Update: This doesn't work because it breaks the server's ability to receive mail) server { server_name mail.domain.com; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } Separate server block for each port (Update: This doesn't work because nginx says there's a conflicting server name and ignores the rule.) server { server_name mail.domain.com; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } and so on for all the other ports Update: I tried this (below) and ran into the same issue as the catch-all server block: server { server_name mail.domain.com; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:143; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:995; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:25; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:110; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:993; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:465; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } I also tried removing the http:// from the start of the proxy_pass lines, but nginx didn't like that.
  11. .6 is the mail server, and .7 is the proxy. .6 is forwarded because I'm not sure what redirection policies to add to the reverse proxy to handle the different mail port traffic. i.e. do I need to prepend http to the address of the mail server? Do I need to add the port to the server name? These are things I don't know, nor apparently, does Google. I'm using a reverse proxy because I have multiple fully qualified domain names with multiple subdomains with web services (http & https) hosted on different servers on my local network, and I need to direct http & https traffic to different machines depending on what the request is. For example gitlab.domain3.com is hosted on the gitlab server, while mattermost.domain1.com is hosted on a completely different machine, and drive.domain2.com is hosted on another completely different server. Also I probably forgot to mention the proxy handles SSL (not on the mail server though). Here's a map of my network. It's not completely accurate, but you should get the idea. I would like the mail server to be behind the proxy, but I'm not completely sure how to do that with the redirection rules. The mailserver works (i.e. it can send and receive mail) in the current configuration (see above) but I can't connect it to outlook because mail.domain1.com, mail.domain2.com and mail.domain3.com go to the proxy resulting in a 502 bad gateway/504 gateway timeout. I don't have any plans for any more web hosting servers, however in my current configuration, gitlab, mattermost, office and drive are all on separate machines but have web interfaces. This is a form of redundancy as if a single service breaks, the issue is isolated to a single machine and all the others are unaffected. I'm probably only ever going to have a single mail server, because with postfix I know it's possible to host multiple domains, e.g. emails addressed to user@domain1.com and user2@domain2.com are both delivered to the same mail server. I hope this is helpful, and believe me - absolutely no offence taken
  12. Hi everyone, I apologise if this is posted in the wrong subforum, it was a toss up between this and Networking. Background Information I few months ago I posted this thread asking for any suggestions on how to install a mail server behind a reverse proxy. Now, I've done it - mostly. For the initial installation of postfix and s-nail, I used this guide from digitalocean which allowed me to get the server up and running to send and receive mail to and from my three different domains, although without SSL. To secure the server with SSL and authenticate users, I followed this guide from UpCloud. The server is still capable of sending and receiving emails, through the command line. I've port forwarded all the mail ports (see below) and sent all mail port traffic to the mail server (.6). (For those wondering, my router is OPNsense, which a fork of pfSense. My friend set it up for me and I'm still not entirely familiar with it, but I do like to think I know what I'm doing regarding networking/server admin. Or maybe not, if this post is believed ¯\_(ツ)_/¯) All other traffic goes to the reverse proxy (.7), which is then distributed to all the different services I have on my network (GitLab, Mattermost, Web, etc). There is a wildcard subdomain rule in the nginx config that takes all non existent subdomains and throws you onto the domain landing page. Therefore I added a mail.domain.com redirect and pointed it to the mail server (below): server { server_name mail.domain.com; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } For the other services, I append the proxy_pass with a port, usually 80 for http. EDIT: I forgot to mention on the reverse proxy and mail server I allowed ports 80, 443, 143, 995, 25, 110, 993 and 465 through Ubuntu's UFW in case that was causing any issues. It wasn't. Problem #1 When I go to add my email account to outlook, it says it can't connect to the incoming mail server (this is using my linux account credentials - there's a linux user for every mail recipient) and returns a 504 Gateway Timeout. Problem #2 In the advanced options of the outlook account configuration, should I use the same mail address (mail.domain.com) and the same port for incoming and outgoing mail? Outlook autofills this with different ports, so maybe I'm thinking I need to have two mail servers, one for incoming and one for outgoing mail? It's entirely possible that every combination of these settings I've tried so far has been wrong. (also should I tick the 'Require logon using SPA' box? I don't know...) Problem #3 In the event I have got the proxy redirection policies wrong, should I route all traffic through the reverse proxy and have specific rules for each port? Kind of like this: server { server_name mail.domain.com:995; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:465; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } server { server_name mail.domain.com:993; location / { proxy_set_header Host $host; proxy_pass ""; proxy_redirect off; } } ... or can you not do this? Do I also need to/should I allow http traffic into the mail server with a redirection policy like the above for user authentication? I have tried to include as much information as possible, hopefully it makes sense. Also thanks for reading, any help/advice is really, really appreciated
  13. This is brilliant, thank you! This is quite an elegant solution, that probably blocks a lot of the Windows 10 data collection as well. I would do this, however there are other Windows 10 PCs on my network that may need access to the microsoft store and normal Windows Update. Thanks for your replies
  14. Hi everyone: I've got an ESXi host with about 15 virtual machines that I perform incremental backups on to a Windows 10 machine using the free edition of Veeam Backup and Replication. For about a month, it's been fine. The Windows 10 backup machine hasn't restarted due to updates, until at least a few days ago. As a result, I haven't been getting daily backups of my environment. I only noticed today when on a whim I decided to remote desktop into the Windows 10 machine to find that it restarted for some reason a few days ago, probably because of Windows Update. I am wondering if there's a foolproof way of completely preventing Windows 10 from restarting. Here's a screenshot of my Windows Update Group Policies: Should I enable/disable any others, or is there another way to prevent Windows from restarting? I don't really want to go the 'defer updates' route because at the end of the period you deferred the updates for I believe you must restart. I suppose I could deal with monthly or quarterly restarts but I'd prefer to know when it happens. Also I'm sure there are better backup methods than Veeam, and it's probably blasphemy that I'm running it on standard Windows 10 (although I did try the evaluation of Windows Server, but that shuts down every 10 days - not ideal), but it works good enough for what I need it for (except for the automatic restart thing). Also, let me know if you think this is a good idea: the group policy No auto restart with logged in users for scheduled automatic updates installations - does that mean a remote desktop logged in user would prevent Windows from restarting? If so I could consider converting the Windows 10 machine into another ESXi host, put another Windows 10 VM on it and then have the backup server and the other VM logged into each other, so neither can restart. This is probably a crazy idea that wouldn't work, but if this doesn't come to anything I might give it a go. Thanks for reading
  15. Okay, so I definitely didn't know what I was doing. Turns out I forgot to enable the DOCP profile for the memory in the BIOS. I enabled that and voila: Hopefully to the trained eye that is a lot better. Having not assembled a Ryzen system and familiar with old Intel based systems (think Ivy Bridge/Haswell), I was looking for something resembling 'XMP'. Thanks for your help though, @Lord Nicoll