Unable to deploy a network from my local Hyperledger Composer playground - hyperledger-composer

I installed Hyperleder Composer on my local machine follow on this https://hyperledger.github.io/composer/latest/installing/development-tools.html
After I started the fabric and playground. The deploy button wasn't able to click.
The button is gray and I can't click it.

Give the name of network admin card and scroll down to credentials for network administrator and change them as displayed in below image.
you can find your answer here

Related

PWA development in localhost

Currently, I am trying to make my website support PWA. After implementing it, it works on the browser from the desktop where the button to install it is available on the address bar, but when I tested it on my mobile locally, somehow it won't prompt the "Add to home screen" popup.
Could the reason be that I run it locally, as it only uses the HTTP protocol? Or I missed something in order to set up for that popup specifically? My website is on Laravel 7.
Hope anyone could help enlighten me with this issue.
Thank you.
UPDATE: Solved it. Apparently by running the website locally with exposed public port using ngrok with HTTPS protocol, I am able to simulate how the app will behave on the mobile and the "Add to home screen" popup finally appeared.
PWAs by definition need HTTPS connections to be installed and run properly (as you said). On your development machine you are making use of the exception for "localhost". On your mobile device, you are not accessing the site locally as it is not hosted on the device itself.

localhost web server on win10 with no admin

so, I want to create a web server and store it into my computer (it's a win10 btw) and i am not the admin.
and when I search localhost it shows an image that if I click it will send me to the IIS site.
pls help me.
Disable it IIS :)
there is no reason to install it or have it installed if you dont use it
Hit the Windows-key type: "Add or Remove Programs". If you get the new Settings app of win10
You have look to right top corner
from there click Add/Remove Windows Components.
Select the Internet Information Services (IIS) uncheck box, click Next, then click Finish.
than try to host your server again

I cannot click capture button to capture virtual machine image

I cannot click Capture (2nd last button "캡처" in Korean) button in Azure portal.
All other virtual machines are same to this situation.
Yesterday, I captured image by clicking that button, but today I cannot click it.
Could you let me know why this happens and how I can solve this problem???
One more question!
this is error log
Provisioning failed. OS Provisioning for VM 'master0' did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image:
* Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
* Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/. OSProvisioningTimedOut
I use a Linux machine
1.You need stop your VM firstly. Stop the VM by usgin Azure Portal.
2.Create your VM image on Azure Portal.
3.Create new VMs by using the image.
Also, you could use PowerShell to capture image, more information please refer to this link.

TomEE Service will not allow to access the application from another LAN Machine

I have deployed my webapps in apache-tomee-plus-1.5.1 and start the server using startup.bat in a windows VM. It's working fine and accessible from any other LAN machine using VM's ip, i.e., 192.168.1.236:8080/archiva.
Now, I want to install the server as a service. For that I have install a service using "service.bat install Archiva" command. When I start the service the application is working fine using localhost/192.168.1.236 from the VM. But not accessible from other LAN machine.
FYI, when I start the service the tomcat home page is shown after hitting 192.168.1.236:8080.
Please help.
Go to Windows Start --> Control Panel
Open Windows Firewall(If not showing, please search it and open).
Click on Allow a Program or Feature through windows firewall
see image...
Click on Change settings and then Allow another program...
Then add all the TomEE.*.exe and press ok.
see image...
Restart your service and application is available from LAN.

Can't access internet after installing vagrant?

I was following this new edx course on Big data on Apache spark. For setting up environment I was told to install virtual-box and vagrant. After installing box and vagrant I restarted my laptop. My modem was working fine, Windows was showing Ethernet connection active but when I try to open any browser and search it was reported that can't connect to internet. I tried uninstalling both box and vagrant but no use. I even restored my system to state when these both applications were not installed but still I can't access internet. What should I do? I'm using Windows 8.1
Just googled a bit and found this:
http://thomascgreen.com/tech/?p=26
Seems to be a working solution.
In any case this is how I got it working again. First go to:
Control Panel > Network and Sharing Center > Change Adapter Settings
Right click on the connection you are having a problem with. In my
case it was “Wireless Network Connection”. On this menu select
“Properties”.
Notice there is a line here that says “Virtual Box Bridged Networking
Driver”. This is Vagrant watching the connection, is my guess.
When I unchecked the box in front of “Virtual Box Bridged Networking
Driver” my internet connection started working again.
Now at this point I started using Google to find out what was going
on. I never found a solution or reason. After searching I rechecked
the box. And everything started working again.
I would also advice to disable/enable all network cards, from the "network connections" panel. (right click on the networks, open the "Network center" and then go to to "update parameters" (I don't have the exact english labels, my Windows isn't in English). It may fix the issue.

Resources