New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to add API using private IP / APInf umbrella issues when running locally #3718
Comments
Hi, as a workaround for ipv4 IPs you can do like this: |
I am able to enter external public IP for adding API but I am not able to enter internal public IP to network for adding API. |
As you know I am working on APInf installation, and as per my understanding FQDN is needed for installation of APInf. Could you please explain what is the need of FQDN while installing APInf? If FQDN is needed, then a user(doesn't have FQDN) cannot complete it's installation process because in the installation documentation it is not mentioned that "YOUR_SITE_DOMAIN" is FQDN for the same? If yes, we should update it in the documentation as a note so that it can be useful for users installing APInf. |
Hi, there is a branch: https://github.com/apinf/platform/tree/docs/update-install which is used to update the documentation. It is work in progress. FQDN is needed if you use docker-compose script. in the docker compose there is the SLL part, which uses Let's Encrypt. Let's Encrypt does not allow certs without FQDN |
There is one docker-compose-development.yml. Can we use this file to install APInf without FQDN as SSL part is not there in this file? |
I'm testing now what makes sense. Please wait a little. Basically, if you want to run locally, pull both APInf platform code, apinf umbrella code, and run locally. Then no SSL is needed |
Hi, one option is to follow Development installation with Docker and add entries to hosts file, remove ssl parts from docker-compose.yml, add the "apinf.dev" to env.apinf and api-umbrella.yml. this allows to run api umbrella locally, and I can curl -k https://apinf.dev:3002 unfortunately this leaves the HSTS config on, so I have not been able to bypass this. I highly recommend to get a domain name and follow the "With Docker Compose -WORKING" part this has been verified to work by me yesterday. I apologise that the umbrella docs are not upto standards, but we are working on this |
Thanks ilarimikkonen. |
Hi, With FQDN this is working if you refer to these instructions: https://github.com/apinf/platform/blob/docs/update-install/INSTALL.md (section With Docker Compose -WORKING) There is a possibility to generate certs and tell umbrella (ssl_cert: and ssl_cert_key: ) to use those. We'll investigate, there is a problem with umbrella loading the cert and key. |
this tested running ubuntu with chromium. Hi, short update; with NREL umbrella we are able to set up locally: easy way: modify api-umbrella.yml and add override_public_http_port: 443
navigate to https://apiumbrella.example.com:3001 umbrella thinks that SSL traffic is terminated somewhere else. HARD WAY with certs:
|
doing this with APInf umbrella leaves some functionality out; we are investigating |
Will the basic functionality of umbrella work such as API add, publish and accessibility? Could you please elaborate which functionalities will not work? |
those features you have mentioned above are NOT working, since the login to APInf umbrella is not working. How ever, they seem to wrk fine with NREL umbrella. NREL umbrella is missing some FIWARE integration features, but basic set is there and is usable. |
Thank you for your valuable guidance and support. As you suggested, I have tried apinf set-up with docker-compose with proper domain name. And it is working fine. |
about the fiware problem, I need to investigate. |
As per my investigation, the private IP falls in below range: |
I am not able to publish API on APInf with bare private IP address while the same API i am able to publish on API-Umbrella.
I have used latest version of APInf and API-Umbrella and followed the steps given at below URl for installation:
docker installation
The text was updated successfully, but these errors were encountered: