I am trying to connect Readthedocs and Gitlab to each other via gitLab OAuth 2.0, I say connect with gitlab without any problem via readthedocs, gitlab connects and I select authorize, but the following error appears, what could be the source of this problem?
thankyou for support.
HTTPSConnectionPool(host='gitlab.tutel', port=443): Max retries exceeded with url: /oauth/token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f22cac5fc10>: Failed to establish a new connection: [Errno 113] No route to host'))
Related
I want to make a connection from Airflow to Google Cloud. I have made a service account in Google Cloud, downloaded the JSON file, and saved the JSON file inside the docker.
I am following this https://cloud.google.com/composer/docs/how-to/managing/connections documentation, but it returns the following error:
HTTPSConnectionPool(host='oauth2.googleapis.com', port=443): Max
retries exceeded with url: /token (Caused by
NewConnectionError('<urllib3.connection.HTTPSConnection object at
0x7f765dfbeb10>: Failed to establish a new connection: [Errno 113] No
route to host'))
Am I doing something wrong or is there an update on the documentation?
Nb:
I use Apache Airflow 2.4.2
I already tested the service account JSON file and it works perfectly to upload data using Python
You can create a connection to Google Cloud from Airflow webserver admin menu. In this menu you can pass the Service Account key file path.
In this picture, the keyfile Path is /usr/local/airflow/dags/gcp.json.
Beforehand you need to mount your key file as a volume in your Docker container with the previous path.
You can also directly copy the key json content in the Airflow connection, in the keyfile Json field :
You can check from these following links :
Airflow-connections
Airflow-with-google-cloud
Airflow-composer-managing-connections
My webhook endpoint is HTTPS secured and the app is running at port 3000
The backend code is Node js.
endpoint e.g: ssl_secured_website:3000/notify (POST)
When I Hit on Test Webhook I get this error: Error:
An error occurred in connecting to the endpoint: ssl_secured_website:3000/notify
I tried port 80, 443 nothing is working
I am actually able to get 200 Response via POSTMAN
As soon as request is received, I am immediately returning 200 status
Error Screenshot
We are trying to integrate OAUTH in superset.Superset installation is currently not secure and running on Http, however, SSO end points are SSL enabled. We are getting the error -
HTTPSConnectionPool(host='sso.company.com', port=443): Max retries exceeded with url: /platform-sso-server/token (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1131)')))
Is there a way to disable the SSL certificate verification.
I have tried adding below lines in superset_config.py, but it didn't help.
import ssl
ssl.SSLContext.verify_mode =ssl.VerifyMode.CERT_NONE
I am on superset 1.3.2 version.
could try put these code in supserset_config.py
import ssl
try:
_create_unverified_https_context = ssl._create_unverified_context
except AttributeError:
pass
else:
ssl._create_default_https_context = _create_unverified_https_context
I'm trying to create a new API from a rest service in WSO2 Publisher and I'm getting an error when I try to validate the endpoint:
When I go to log it shows the message:
[2021-03-30 22:09:54,744] ERROR - ApisApiServiceImpl Error occurred while sending the HEAD request to the given endpoint url:
java.net.ConnectException: Connection refused (Connection refused)
What am I doing wrong?
If I progress the creation when I try to test I get another error:
[2021-03-30 22:15:31,311] WARN - SourceHandler I/O error: Received fatal alert: certificate_unknown
[2021-03-30 22:15:31,351] WARN - ConnectCallback Connection refused or failed for : localhost/127.0.0.1:8888
[2021-03-30 22:15:31,353] WARN - EndpointContext Endpoint : CpoExecutorAPI--v1.0.0_APIproductionEndpoint with address http://localhost:8888/cpo-executor/dev will be marked SUSPENDED as it failed
Apart from the certificate issue, another possible cause for this error is network connectivity. Please make sure that there weren't any network issues while invoking the request and the network connectivity was stable. Also, please check whether you can directly connect to the provided endpoint URL and get the responses without any issues.
WARN - SourceHandler I/O error: Received fatal alert: certificate_unknown
With the above-mentioned warning, we can suspect there is an issue with certificates.
Therefore, if you have made any recent certificate changes in your environment can you check whether the required certs are available in the API Manager Keystore?
I'm using the <f:websocket> to update a chat page.
The app is running in Wildfly 20 and it's working perfectly in localhost but the websocket is giving the following error over the EC2 AWS instance.
jsf.js.xhtml?ln=javax.faces:1 WebSocket connection to 'wss://app.mydomain.com/javax.faces.push/incomingPush?8c34119c-cd10-41ca-bc13-65494ce18d4f' failed: Error during WebSocket handshake: Unexpected response code: 404
I also found this error in the wildfly log, that I think it has something to do (since in localhost I don't get this error):
2020-12-17 18:40:44,641 ERROR [org.jboss.weld.Bean] (default task-9) WELD-000019: Error destroying an instance com.sun.faces.push.WebsocketChannelManager$ViewScope#6d608a43 of Managed Bean [class com.sun.faces.push.WebsocketChannelManager$ViewScope] with qualifiers [#Any #Default]
I've been stuck with this problem for a week now. Any help would be greatly appreciated.
Thanks!