I banged my head against the desk for way too long trying to figure out this issue. While trying to authenticate with Netsuite’s REST API instead of SOAP, I got the same INVALID_LOGIN_ATTEMPT error.
The fix? My account ID, which was a sandbox and included the letters S and B, had to be capitalized. I was using lowercase letters. Changing them to uppercase letters did the job!
I have an Ubuntu VM running in Hyper-V (or HyperV if you’re lazy) that I had to expand. I used the GUI in Hyper-V Manager to add some space first and rebooted my VM. After that I was able to utilize the new space by following these steps:
First, open Up Disks app and make sure your “VM” is seeing the free space
After that, open up terminal and install some cloud tools that’ll help us out.
sudo apt-get install cloud-guest-utilsAfter that, run this command to use all that sweet new space.
sudo growpart /dev/sda 1That’s it! It grew to use all the free space and we were good to go.
I ran into this one today on a fresh Ubuntu install. I was attempting to mount my NAS and configured fstab. I went to mount the share and got this error:
mount: /media/Data: cannot mount //[SHARE]/Data read-only.
The fix was to install cifs-utils via apt-get install cifs-utils
Afterwards, I was able to mount the share successfully. Of course, there may be a few other causes for this error so be sure you fit this scenario.
A real hand-banger of an issue thanks to Microsoft’s love for hiding settings behind classic admin centers. After enabling Office for Web and OneDrive (or Sharepoint) for several users, they were unable to edit Office documents in Office Online / Office Web Apps via www.office.com. They didn’t even show up!
What Was Being Seen:
What Should Be Seen:
The resolution was classic Microsoft. After making sure that the users had the correct applications assigned, namely Office Apps for Web and either SharePoint or OneDrive, we had to navigate to the SharePoint Admin Center, click on Settings, and then classic settings.
Once there, the first option was the cause of our trouble. Make sure you don’t hide the icons!
I’ve had to do this at a job recently that had to monitor access to sensitive offices and vaccines. This works internally (with a double-NAT) or over WAN with a change or two
Essentially, the steps are:
1) Setup camera with static, local IP
2) Login to camera and configure NVR IP as the WAN IP of the UDM Pro / NVR
3) Login to UDM Pro and configure WAN Local Firewall Rule to allow all traffic from static IP you set in Step 1 (if going over WAN, use WAN IP of location with Ubiquiti camera)
4) Login to Protect app in UDM Pro, add camera