Razer Blade 15 microphone isn't working or doesn't pick up any sound. Don't worry its a simple fix, follow the steps below.
The Razer Blade 15 comes with a Realtek Microphone installed near the camera in the bezel.
The issue arises from the Realtek software that comes pre-installed on the Razer Blade 15.
Head to Realtek Audio Console and open the microphone section
Turning off Microphone Effects 'All Off' fixed the issue. The microphone started working correctly again.
By Default NGINX logs all IPs going through the reverse proxy. The log will keep growing in size.
To ease of maintainance and troubleshooting, it is advisable to get NGINX to create a new access.log everyday.
If NGINX is running on Windows this can be accomplished using a BAT file.
Create a new BAT file with the following
REM ECHO %YEAR%
REM ECHO %MONTH%
REM ECHO %DAY%
move C:\nginx\logs\Access.log C:\nginx\logs\Old_Logs\Access_%DATE_FRM%.log
move C:\nginx\logs\Error.log C:\nginx\logs\Old_Logs\Error_%DATE_FRM%.log
call C:\nginx\nginx -p C:\nginx -s reopen
Change the Path to the path of your NGINX Log folder. Also create a new folder in the 'Logs' folder called 'Old_Logs'
Save the BAT file.
We now need to create a Scheduled Task to run this BAT file once a Day.
Create a Basic Task
Daily Task or Weekly depending on how often you want to create a new log.
Choose a Time for it to change logs, i chose 00:00:01 so it would create a new log after midnight.
Next select the location of the BAT file and click next until your seen the screen below.
Make sure to put a tick in the 'Open the properties dialog....' box and click finish.
For The Task to restart NGINX the same user has to run the Task Scheduler and the Service.
Select the correct user in 'Change User or Group' and tick the 'Run with highest privileges' box and click 'ok'.
Next run 'services.msc'
Find your NGINX Service and right click on it 'properties'.
On the 'log on' tab change it from 'Local System Account' to 'This Account' and enter the same username as you did for the Task Scheduler.
Finally click Apply and Ok. And that's it. The task will run, move the access.log to the new folder and rename it with the date. NGINX will then create a new access.log file and repeat.
You own a domain name and you use Cloudflare to proxy your websites, services or something else and now you want to have an email address with your new shiny domain name. Cloudflare doesnt support mail forwarding, some registrars have their own forwarding system but if you use Cloudflare then we need to look at Mailgun.
Once added you need to verify you own the domain and setup the relevent records. Head over to Cloudflare and create the records, they will look similar to the below image.
This is what you will end up with. (Make sure the email CNAME status is the grey cloud!)
Head back to Mailgun. You will need to give the Records we created above some time to propogated across the internet. You can check this by clicking 'Check DNS Records Now'
Creating Routes. In Mailgun we need to specify routes or email addresses. This will define the recipient email and the action to take.
You can create a number of routes or you can create a 'catch all' or both. Priority is like rules, It will match the lowest priority first (lowest number), so if you set a 'catch all' rule set a high number priority e.g. 100. That way it will attempt to match everything else first.
Finally in Mailgun we also need to validated our personal email address, hotmail, gmail or whatever. Head into Account Settings and then Authorised Recipients. Add your email address which will send a link to your email which you need to validate.
Once the DNS settings have been updated and you have validated your email you should now be able to receive any emails sent to *@mymedia.cf which will appear in your hotmail or gmail account.
All Sonos players attempt to establish a peer-to-peer wireless mesh network known as SonosNet as soon as they are powered up. While this is convenient, there are several situations in which turning off this WiFi connection makes sense:
You own a single player that you connected directly to your home router with an Ethernet cable. You don't need the built-in SonosNet, so why not deactivate it to reduce power consumption and electromagnetic radiations.
SonosNet relies on the spanning tree protocol (aka STP) to function properly, so if your other network equipment doesn't support this functionality your entire network will be overloaded by broadcast storms and frequently crash.
Instead of upgrading your network it is much easier and cheaper to eliminate the source of the problem.
You're worried about WiFi-Jacking. Why leave a backdoor in your network that can't be strongly secured?
It is possible to switch on or off the wireless adapter of each Sonos player individually. Here's how in 3 simple steps.
Step 1: Finding the IP address of the device
From the Sonos controller, click on the "about my sonos system" menu. You should see something like this:
Serial Number: 00-0E-58-2D-B0-C3:3
Version: 4.2 (build 24071060)
Hardware Version: 18.104.22.168-1
IP Address: 192.168.1.27
In the example above, the address is 192.168.1.27. We'll refer to it as in the rest of this article.
Step 2: Checking the status of the Wifi link
Sonos provides a little known on the port 1400 of their players that you can access from any web browser at the following URL:
You should see something like this:
The entrie labeled 'eth0' and 'eth1' correspond to the 2 wired ports. The 'lo' and 'br0' interfaces are virtual networking devices used internally by the Linux kernel. The entry we're interested in is labeled 'ath0', which stands for Atheros device 0. Atheros is the manufacturer of the embedded WiFi chip.
Step 3: Disabling the link
To disable the WiFi link start by issuing the following HTTP request:
You should get the following answer:
wifictrl request succeeded HTTP 200 OK
You can also check that the link has indeed been disabled by going back to the status page. The 'ath0' entry should not be present anymore. The setting is not persistent, so if you happen to be unable to connect to your player after disabling the WiFi you can undo the change by power cycling the player.
If you want to disable the WiFi link for good, simply issue the following http request:
The change will now be preserved even after an upgrade. If you ever need to connect the player wirelessly in the future you can turn the WiFi back on as follow:
Impact on power consumption
I measured the power consumption of several players with a wattmeter which is accurate to +/- 0.5 watt. Turning off the WiFi link reduces the power consumption of the players by about 2 Watts. Here are the results measured when the players are idle:
Wifi On = 6.5W
Wifi Off = 4.5W
Wifi On = 4W
Wifi Off = 2W
--domains "mydomain.com,emby.mydomain.com" (list all your domains you want the cert to cover - i think max is 50~)
--path E:\NGINX\html.well-known\acme-challenge (change E:\NGINX to your NGINX locaiton, keeping the html.well-known....
when you hit enter it will test your setup for the correct files and config, it basically gets a fake certificate. if this completes with no errors you now need to add the argument --live to the end of the script above, like so
hit enter and it should go off an fetch your real domain.csr account.key and domain.crt and domain.key. these will be downloaded into the le64 folder. Keep the csr and account.key safe, you will need these for renewal.
Now you have all this setup you can re-run the above le64.exe script come renew and its all done.
You've probably stumbled across this page if like me you were trying to find a way to install a shared printer to all users on a Windows machine.
By default a shared printer only gets installed to a users profile, when the next user comes along the printer needs to be reinstalled.
Normally you can install the printer using a local port or TCP-IP port which would then work for all users. However if you use a printer server or just shared it from another machine then you need to know the hack below which will install it for all users.
Step 1 - Printer Server/Shared Machine
Install the printer as you normally would on your print server. Either using a local port (USB) or TCP/IP (Network) and drivers.
Make any changes to the printer, trays, adding x86 and x64 drivers, set security permissions.
Share the printer
Step 2 - On the remote machine
Open up CMD and run as administrator
Copy the below into the CMD window, changing \\servername\printer to your details.