In the crypto world DApps should run in a type of server, in the case of Ethereum is the EVM the equivalent to a server like Nginx or Apache?
Related
I have my Eureka server running on a remote raspberry pi. I have other Eureka clients on other pi's and they are working fine. I'm trying to run another client on my laptop but when it registers with the Eureka service it is registering as localhost. Obviously this will not work because the client is not running on the same host as the Eureka server. How can I get my client to register it self with the actual hostname (or IP) instead of localhost?
You can either set eureka.instance.hostname="your-host-name" for the client in its config to whatever you want it to register with, or try setting eureka.instance.prefer-ip-address=true
See https://cloud.spring.io/spring-cloud-netflix/multi/multi_spring-cloud-eureka-server.html#spring-cloud-eureka-server-prefer-ip-address
can't communicate with my Hyperledger Fabric's First-Network...
I can query and invoke from inside CLI docker container. Works fine!
But if i want to use Postman and Json to invoke or query from a client PC, than i get an error message in the orderer log:
[grpc] Printf -> DEBU fc9 grpc: Server.Serve failed to complete security handshake from "10.xx.xx.xxx:56694": tls: oversized record received with length 21536
The docker containers are on Suse Linux Server and not on locally VM.
I can ping my server and the Orderer-Container Port is mapped as default config(7050:7050)
I don't really know where to find the right cert.pem and key.pem files on the linux server filesystem. Tried different one in Postman = Option client certificates.
Also tried to search a solution but can't find a working one.
Hyperledger Fabric Peer and Orderer nodes only support direct communication using gRPC (which is protocol buffers over HTTP/2) APIs. They do not offer an HTTP/REST interface. Postman only supports HTTP endpoints so it will not work with peer or orderer nodes. (the error you see if also likely due to the fact that postman was not using HTTPS).
If you want to attempt to use REST with the peer and orderer nodes, you might want to check out https://github.com/hyperledger/fabric-sdk-rest which aims to provide a REST server in front of Hyperledger Fabric nodes.
I have built a working IBM api connect service (loopback) that provides local mySQL data to/from an angular website. I now want to move this service to an Ubuntu web server (appache) so that I can open up the website to external traffic. I have moved installed api connect onto the server and moved the project files across.
But I don't understand how to run the project so that it is available externally. When I run API connect the api is available on a local port address: Web server listening at: http://127.0.0.1:9000.
But in my webpage (angularjs) I can't call this as it tries to connect on the client machine, not server.
Has anyone done this before and if so, can you offer any advice?
You should configure your Apache as a reverse proxy, so that it forwards requests from your public ip address at port 80 (or 443 if you want SSL) to localhost:9000. See https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html or https://www.nginx.com/resources/admin-guide/reverse-proxy/ if you'd like to try out Nginx.
I'm using Xampp server (Apache server ) for my website however it has some connectivity issues with the internet and I can't access it online. So I was advised that I must use Windows server 2008. Let me know if this is a good idea or not. The Xampp has issue with port forward through Dynamic IP. Let me know the best option that I have.
To connect your Apache webserver to the internet you don't need to do any local port-forwarding, you should try port-forwarding with your router. If you're runing linux, you should type ifconfig and look for your default gateway, that's the ip your router is using.
Some ISP's force you to use their own website to port-forward though. Standard, apache always runs on port 80, which you should allow in your firewall using the TCP protocol.
Perhaps you could explain your situation more, Windows Server won't make the hosting easier though. You will most likely encounter the same problems.
I've got an internal docker registry, internal DNS, etc. Access to the larger Internet is blocked except http/https via a proxy, which I'd like to avoid anyway. UDP calls to 8.8.8.8 are also blocked, in case you're wondering. I'm trying to set 2.7.0 up on Ubuntu 16.04, but the simplest hello world tutorial just hangs.