What is CURVE I : cannot open client INITIATE vouch? - volttron

I have a problem about forward historian.
I install volttron_central on PC called A, and then instlal volttron_sub on Raspberry pi.
I entered the command 'vctl auth keypair' on volttron_central, and then I got the serverkey and secretkey.
and I install forward historian on volttron-sub, and running volttron-sub & volttron-central.
but I saw that 'CURVE I : cannot open client INITIATE vouch' on VOLTTRON_Central terminal.
I want to install forward historian on volttron-sub and send device(Philips-Hue) information to volttron-central machine.
Do you know how to solve this problem?
Thank you.

Login to PC called A. From a volttron enabled console volttron-ctl auth serverkey. This will give you the serverkey that you will use in any remote connection to PC called A.
Login to volttron_sub and get the publickey from the forwarder and voltron central platform agents by running vctl auth publickey
(Back on PC called A) add the credentials from the forwarder and volttron central platform using vctl auth add --credential <publickey> for each agent.
NOTE: These instructions are assuming you are using releases 5.0 rc branch.


Azure IoT SDK - connection not accepted problem

I am using the Azure IoT SDK for C to try and provision a device on my hub on the Azure IoT Portal.
I have followed the instructions in order to generate signed certificates and add them to the portal as stated here https://github.com/Azure/azure-iot-sdk-c/blob/master/tools/CACertificates/CACertificateOverview.md
and also here in this tutorial https://kevinsaye.wordpress.com/2020/04/14/using-a-real-certificate-with-the-azure-iot-client-c-sdk-and-the-provisioning-service/ .
When I run the sample code prov_dev_client_ll_sample.c with all my changes, I am continuously getting the below authorization error. I have built and run code this for an X86-64 chip running Debian, and also cross-compiled for an ARM chip, both yielding the same error.
On the Azure Portal, I have tried to create an enrollment group associating the certificates, and also tried to create an individual enrollment, explicitly adding the certificates. Nothing works. People have suggested that my clock might be out of date. However, it looks fine when I run date .
Any help would be greatly appreciated. I am more than two days trying to solve this issue now.
Running provisioning appplication..
Provisioning API Version : 1.3.8
Iothub API Version: 1.3.8
Device Certificate Name File: Device_identity.txt
Device Certificate PEM File : Device_cert.pem
Device Private Key PEM File : Device_key.pem
Error: Time:Fri Jun 19 12:02:42 2020 File:/home/azure-iot-sdk-
c/provisioning_client/src/prov_transport_mqtt_common.c Func:mqtt_operation_complete_callback Line:208
Connection Not Accepted: 0x5: Not Authorized
Error: Time:Fri Jun 19 12:02:42 2020 File:/home/azure-iot-sdk-
c/provisioning_client/src/prov_transport_mqtt_common.c Func:mqtt_error_callback Line:139 MQTT
communication error
Error: Time:Fri Jun 19 12:02:42 2020 File:/home/azure-iot-sdk-
c/provisioning_client/src/prov_device_ll_client.c Func:on_transport_registration_data Line:771
retrieving data from the provisioning service
Failure encountered on registration PROV_DEVICE_RESULT_DEV_AUTH_ERROR
registration failed!
Press any enter to continue:
There are two distinct scenarios for using an X.509 cert to connect a device to an Azure IoT hub:
Register and connect the device directly with your IoT hub
Use the Device Provisioning Service to assign and register your device to an IoT hub so that it can connect.
This sample shows you how to connect a device directly to IoT Hub without using DPS: https://github.com/Azure/azure-iot-sdk-c/tree/master/iothub_client/samples/iothub_ll_client_x509_sample. The sample assumes you're using the scripts described in https://github.com/Azure/azure-iot-sdk-c/blob/master/tools/CACertificates/CACertificateOverview.md to generate your keys and certs. For more information, see: https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-x509ca-overview.
This sample (the one you're trying to run) shows you how to use DPS to register your device with IoT Hub: https://github.com/Azure/azure-iot-sdk-c/tree/master/provisioning_client/samples/prov_dev_client_sample. The sample uses a simulated Hardware Security Module (HSM) to generate the keys and certs (not the scripts). For more information about how to run this sample, see https://learn.microsoft.com/azure/iot-dps/quick-create-simulated-device-x509.

Can't POST credentials on OCN client

I have a problem with OCN-client.
When I call POST http://host/ocpi/2.2/credentials, response:
Role with party_id=ABC and country_code=ES not listed in (truncated)...
Means that I have to register our company?
How I can do it?
Yes, the client will not accept the credentials handshake if you are not already listed in the registry. Running the registry locally will create a new network only existing on your local development environment. To do this, you would also need to point the OCN client to your local network in its configuration. This is good during development, though there will be no other MSPs/CPOs to interact with out of the box (see https://bitbucket.org/shareandcharge/ocn-tools for how you could do that yourself). Once you are ready, you could then access our public test environment via your local OCN client (the default configuration values point to it), or connect to one remotely.

how to self-hosting a website on ubuntu 18.04 system and using lampp server?

I'm trying to self hosting a website on ubuntu 18.04 system and using lampp server. i can not access the site through my public ip address. can anyone help me out?
i have also created a virtual server in my router. but till something is wrong.
you can do that by logging into the router which provides you the internet …
then make port forward to all the requests that coming from external under port 80 ( which is the http browsing port ) and forward it to the IP which has your ubunto OS …
you may as well add RDP connection if you have windows , in short , you will have to find the responsible port which works for each protocol and then forward it to your ubunto OS
like https , will work under 443 so you may as well forward it if you wan your website to work securely as https .
as for the domain name … you may use services fore free like DYN.com or noip.com
some routers btw can accept logins directly from dyn and noip and other similar websites which provide the dynamic hosting service .

Public LAMP with a modem and router

I am using an Apache2 with a PHP and MySQL installed on Ubuntu. What I would like to do is to run the server public, to access it from outside my network.
However, I am having trouble configuring it, since I am using a ZyXEL P660HW-T3 v2 ADSL Modem with an IP 90.xxx.xxx.xxx together with an ASUS RT-N16 Wi-Fi router with the LAN address
Could someone help me to set up the configuration file correctly to make the server public?
You need to configure your router to forward port 80 from the WAN interface to

Is there any open source for Ip Tunnel?

I need one server to receive ip requests from clients(there are not in the same intranet), and I can
route all the response packets to a special gateway server, and then I send the response packages to
clients after some processing. it is like VPN, but I want to do some development based one
opensource project, so i can control it myself.
any suggestion? thanks!
There is OpenVPN which is as the name already suggests open source.
You could set up the server on the local one as a kind of proxy (or reverse-proxy depending on your viewpoint) and have the clients connect to it.
It depends what protocol you're using, maybe it has explicit proxy capability or you can get an existing proxy program, or just proxy it using a simple socket forwarder program.