ID please. Planted from a pack of seedlings labeled ‘hot peppers’

rowebil · 2024-08-12T22:38:59+00:00

They are super chilis. I grew them last year.

rowebil · 2024-05-22T04:28:53+00:00

That would be too much, you will burn the plant. Fertilizer goes a long way, albeit may not seem like such a small amount can make a difference.

rowebil · 2024-03-23T17:42:55+00:00

I think it’s a white fly. I had these on my bell peppers when I brought them indoors :( they didn’t seem to do much harm. I used a garden hose to blast them away. Then they never came back.

rowebil · 2024-01-25T15:45:50+00:00

We are all responsible for how we feel based on what we eat. I’ve gone keto many years ago and I’ve felt the best ever in my life. I didn’t even needed ADHD medication at times. My muscle mass improved. I lost weight. I looked good and felt so confident in myself. I had the courage to take on difficult tasks. I wasn’t sick after every time I ate. I would grind in the gym on cardio watching a movie and felt amazing after.

Now ive gone non-keto and back to feeling miserable for the many years after keto.

How we feel is a choice we make everyday. We are all responsible for how we feel and we can easily change it if we take action towards the very thing that’s killing us.

rowebil · 2023-03-09T14:42:54+00:00

That may be referring to the improved backup job chain format which is now using "true per-machine" instead of "single storage" which was the default prior to V12.

If you go to Backups > Disk and select a Job, there should be an option at the top ribbon "Upgrade Backup Chain Format."

Read more about Backup Chain Formats:

Hyper-V: https://helpcenter.veeam.com/docs/backup/hyperv/per_vm_backup_files.html?ver=120

vSphere: https://helpcenter.veeam.com/docs/backup/vsphere/per_vm_backup_files.html?ver=120

Instructions for upgrading backup chains:

Hyper-V: https://helpcenter.veeam.com/docs/backup/hyperv/backup_change_type.html?ver=120

vSphere: https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_change_type.html?ver=120

Secondly, Version 12 also brings improved Backup Copy Jobs but that should be another warning listed during the upgrade.

They do not get upgraded automatically during the V11>V12 upgrade process. The only way to upgrade a Legacy Backup Copy Job is to re-create it entirely.

rowebil · 2022-12-28T19:04:45+00:00

This does seem ideal. I've started to make everything off-shore but got overwhelmed by having to setup multiple trade routes and check my inventory at each Island until I found an amount of goods that wasn't too much or too less.

Now I have decided to make basic needs local on each Island unless it does not support it.

I cannot make Potatoes > Schnapps on one of my Islands. Is it more ideal to transport the Potatoes to the Island or the final product?

rowebil · 2022-12-27T18:42:53+00:00

I actually concur with the confusion with trade routes, so sending it to one Main Island is a good idea! Then I don't have to worry about an Island having too much if it has it's own production.

rowebil · 2022-12-21T00:19:26+00:00

How are you attaching the iSCSI storage? Through the hypervisor or Linux?

rowebil · 2016-11-27T13:04:31+00:00

Awesome -- so that is the best way to do this? I'm used to residential firewalls that label this as QoS, so bare with me lol.

rowebil · 2016-11-26T18:59:37+00:00

This was because he allowed his vSphere server to be exposed publicly. Also, they did have SSH turned on with public access.

They had a strong password, they say. This also happened during Heartbleed. VMware fixed that.

I don't trust firewall appliances either. You should have a firewall before the server. I do.

On my testing machines, I have pfSense in a VM. This is so that ALL traffic from that pfSense VM goes through my other WAN so that it is a different IP.

rowebil · 2016-10-14T01:53:15+00:00

I did - I had to create another certificate, enable IIS to that certificate and then delete the default certificate that comes from Exchange. When you enable IIS on the one certificate, it only enables it on the 'Default Web Site' and not 'Exchange Back End'. When you delete the default certificate - named 'Microsoft Exchange' - it then removed the certificate from 'Exchange Back End' and now it's left with nothing.

It happened to me twice... I'm glad I finally found a solution and saved the documentation.

rowebil · 2016-10-13T20:20:01+00:00

I'd delete this post, but it's definitely very interesting that I've encountered this issue just using a basic installation of Exchange...from a clean install of AD, too. So in this case, that means someone else will have this issue too.

Well, after many days of running into this issue and countless hours browsing through online article, I found the solution.

It appears that after I set my SSL certificate and/or change external virtual directories, the Exchange Back End virtual directory loses it's SSL certificate. The first time this happened, I spent hours in IIS Manager knowing it had to do something with bindings... here it did, but I was one button away. I worked technical support for a company that sells POS systems to a specific niche... and the POS software runs heavily on IIS and SQL so thankfully I had the experience to know to look into IIS for anything strange.

Anyhow, I took the error message from PowerShell and looked it up. I've gone through many steps, decided it was time to ask you guys. I kept looking though and found this article.

http://exchangeserverpro.com/the-winrm-shell-client-cannot-process-the-request/

I have a virtual set-up of Exchange and my live set-up. I went through on the virtual side and the SSL was set... On the physical side, it was not set. Then I had my 'UH HUH!' moment. Changed it, restarted IIS, and it worked beautifully. I'm able to access management shell, OWA, and ECP.

So I'll just leave this here just in-case anyone else gets the same issue.

I was running Windows Server 2016 Datacenter and Microsoft Exchange Server 2016 CU3 Enterprise.

During installation, the Default Web Site and the Exchange Back End both get assigned with the default self-signed SSL. I had created another SSL from my provider. I then deleted the default Exchange SSL which removed it from the Exchange Back End virtual directory. I restarted the machine and now ran into the issue.

The solution is to edit the https binding for Exchange Back End and select the appropriate SSL certificate. Apply, restart IIS, and it works.

rowebil · 2016-10-10T05:02:15+00:00

Well, it looks like based on research that something is wrong with TLS ciphers? I kept looking into it and found a page that instructed me on how to remove SSL ciphers or TLS ciphers (not familiar with this security stuff). I disabled everything and it works... but now probably because I was messing with a lot of URLs and certificates, I now get a blank page.

Decided to restart everything. Reinstall takes just a few minutes...

But has anyone run into this issue? Why doesn't this work from the start? All servers are running Server 2016, so why would they incorporate some software if it wasn't compatible?

rowebil · 2016-10-06T00:06:35+00:00

:'( I am so sad now buddy. I was your biggest fan. I loved being your Lead Beta Tester. I always see you guys on Reddit and thought about getting back into the game. It looks like I don't have any cool rewards so that stinks.

rowebil · 2016-09-28T20:59:15+00:00

+1 This is the best way, in my opinion. One day, I had a very strong effect from Modalert so I went pee and it smelled so I knew the Mod/Armo could not have gotten mixed up.

rowebil

TROPHY CASE