AJ_Winslow

think I figured it out... just added a wildcard to the proxy hosts and it did exactly what I needed it to...

I have been using NGINX Proxy Manager (NPM) for a few years now and it works pretty seamless for the most part. I recently switched from Google Domains to Cloudflare because Google sucks (RIP Google Domains and most recently GPay). My setup is as follows: Cloudflare points to static IP but is proxied through cloudflare. Port 80 & 443 are open on my firewall and forward to my NPM server. NPM manages all sub domains correctly. NPM has an origin server certificate that all sub domains use. Cloudflare SSL/TLS settings are set to Full Strict requiring an origin server certificate from NPM. This setup works fine when the user uses a known subdomain, (ie plex.website.com). The issue I am running into is that NPM does not appear to have a way to have the "default site", site shown when NPM doesnt recognize the requested subdomain, use SSL and Cloudflare ends up throwing an "SSL handshake failed Error code 525". Does anyone know how I could get the default site to also use SSL?

@Linus @Luke , run a live stream, no audio, out the front of your building and let people use LTTStore to buy stuff and post merch messages in support. Or just stream the wan set with the LTT Music looping.

Well, after a glass of water i got to thinking... what does inline-block actually do? And well here is a good website to check out to figure out how I found the issue: https://css-tricks.com/fighting-the-space-between-inline-block-elements/ inline-block adds spaces between the elements and with some, "funky" fixes I solved the issue. Opted to ditch inline-block for float. Never really liked float but it will work nice and clean for this.

Alright guys, I have been starring at this code and I cant figure out why I am getting this weird result in Chrome and Firefox. Basically, when I run the first for loop without an end of line the divs display correctly and fit within the parent div. When I add an EOL, whether it is be PHP_EOL or simply press enter between each line, the divs get a funky width or margin (im not sure which). However, when I inspect the divs in Chrome, all their properties are the same; but, as shown in the photo below, there is clearly a visual change! Can someone explain this to me? <div id="Container"> <? for ($i = 0; $i <= 10; $i++) { echo '<div class="StoreItem">'.$i.'</div>'; } for ($i = 0; $i <= 10; $i++) { echo '<div class="StoreItem">'.$i.'</div>'.PHP_EOL; } ?> </div> <style> #Container { position: fixed; top: 75px; left: 75px; right: 0px; bottom: 0px; overflow-y: auto; margin:5px; z-index: 0; } .StoreItem { display: inline-block; margin: 2%; height: 300px; background: red; font-size: 2em; font-weight: 700; text-align: center; width: 21%; } </style> In the image below, the divs created without and EOL output correctly and display 4 across. The second set of divs have an EOL and do not display correctly. <!-- Without EOL --> <div class="StoreItem">0</div><div class="StoreItem">1</div><div class="StoreItem">2</div><div class="StoreItem">3</div><div class="StoreItem">4</div><div class="StoreItem">5</div><div class="StoreItem">6</div><div class="StoreItem">7</div><div class="StoreItem">8</div><div class="StoreItem">9</div><div class="StoreItem">10</div><div class="StoreItem">0</div> <!-- With EOL --> <div class="StoreItem">1</div> <div class="StoreItem">2</div> <div class="StoreItem">3</div> <div class="StoreItem">4</div> <div class="StoreItem">5</div> <div class="StoreItem">6</div> <div class="StoreItem">7</div> <div class="StoreItem">8</div> <div class="StoreItem">9</div> <div class="StoreItem">10</div> Any help or information would be appreciated!

What problem are you having? Not getting IP addresses? If you modem is the bell home hub you can have it hooked up to that. Are you running a DHCP server on both the Google WiFi and the Bell Hub?

It does on FiOS as I have done it multiple times when testing out my ASUS router and having to switch back and forth between the ASUS and FiOS router. Attached is a photo from the FiOS router that shows the ability to Renew. When the router has a WAN IP it says Release. Once clicked it releases the mac address from my ISP and I can immediately connect another router and obtain an IP without having to call my ISP to release it.

The boxes are not on the VLAN, they get their IP from the local DHCP server. Every other router that I own has the ability to release the DHCP Lease. I feel this is a simple function that could be added down the road. As I stated not a huge issue but a slightly annoying one none the less =P EDIT: The IPTV might be apart of the VLAN, I have not done any research into how this works. The boxes do however connect to my local DHCP Server to get an IP so they can access their guide information.

The Issue: Google WiFi stalls and reboots while modifying settings through APP. Upon restart, Google WiFi Cloud Services becomes unresponsive (disabled) and Google WiFi requires factory reset in order to change any setting. I am posting this encase anyone else is having trouble and can not figure out why. So the issue is on the Google WiFi mesh system when used as the primary, internet facing, router on a fiber network (i.e. FiOS) that uses VLAN or DDNS. My original setup was as follows: FiOS ONT (Optical Network Terminal) --> Google WiFi --> FiOS Router --> All Other Wired Devices As listed above, the Google WiFi is directly connected to the ONT and thus received the WAN IP. I then connected the FiOS router to the Google WiFi and disabled the DHCP & DNS server so all DHCP and DNS requests would be sent through to the Google WiFi. All wired devices are connected to the FiOS router which is essentially being used as a managed switch. According to Google, Google WiFi does not support VLAN or DDNS and thus Google WiFi Cloud Services will crash and become unresponsive through the mobile app. This will also cause the diagnostic report function to fail. The Solution: The solution to this issue is simple enough, but does require another piece of hardware. Simply place a network switch in between the ONT and the Google WiFi. The setup should be as follows: FiOS ONT --> Network Switch --> Google WiFi --> FiOS Router --> All Other Wired Devices By placing the switch before the router the switch removes the 4 bits added onto the packets from the VLAN and thus allows Google WiFi to operate properly. My Rant: This is extremely annoying for a number of reasons. First, I bought the Google WiFi router for the ability to manage every device on my network through a convenient app. If I placed the FiOS router before the Google router I would either have to configure it to act as a switch, which means I would loose MOCA connections such as my cable boxes, or set it up as a router and thus loose the ability to manage any device on the FiOS router from the Google WiFi app. Next, by using a network switch before the Google Wifi I remove any VLAN issues but I now have a $25 switch that I am unable to use three of the ports on because it is before the primary router. What is the point of buying the Google WiFi mesh setup if it requires other hardware to properly operate on a fiber network? Finally, this is a small issue but it managed to make my night very long, Google WiFi does NOT allow you to release the DHCP Lease which means, on FiOS at least, I have to call and wait 25 minutes on hold, hang up from frustration, then wait TWO HOURS before the ONT DHCP Lease expires to be able to test that the Google WiFi works behind switch (before going out and buying one). The Conclusion: Google WiFi is an easy to setup and use mesh network that I would definitely recommend to anyone. By simply adding a network switch before the Google WiFi this issue can be resolved. Hopefully, Google will soon support VLAN and DDNS so this issue will go away =]

hmm. are they front usb (chassis) or rear?

Silly question i know, have u tried restarting since you updated the drivers? Are the ports on the motherboard on the back or are they on the chassis?

I wonder if this could solve your issue. *right click* on desktop *click* nVidia Control Panel In "Select a Task" navigate through: 3D Settings - > Manage 3D Settings Go to the "Program Settings" tab Where it says "Select a program to customize:" choose "Google Chrome (chrome.exe)" Where it says "Select the preferred graphics processor for this program:" choose "High-performance nVidia processor" I unfortunately do not have a desktop setup with multiple cards to try this on but I did have some luck when my laptop's integrated graphics became buggy and I needed chrome to run specifically on the nVidia GPU. Obviously, change "Google Chrome (chrome.exe)" to whatever software you specifically want to run on your GPU. Keep me updated as I am curious how this works for you! AJW

What is your GPU temp?

Alright, not much to go on here so lets start with the basics. Is this a new setup or did this issue just randomly start? Is your HDMI plugged into the graphics card or the motherboard's HDMI out? Have you messed with any setting in the nvidia control panel or gforce experience software? Is the FPS low from the start or does it drop the longer you play? Do you have any monitoring software such as MSI Afterburner and could you give us some temp stats? What resolution monitor are u running/what resolution are you trying to play the game at?