I am trying to figure out how to Purge the Akamai cache through the Akamai CLI (version 1.3.1).
I am using a ~/.edgerc with :
[default]
host = *.luna.akamaiapis.net
client_token = akab-****
client_secret = ****
access_token = akab-****
These credentials provide access to the following settings:
API service name: CCU APIs
Description: Content control utility APIs
Access level: READ-WRITE
When I execute the following command in my Mac terminal:
akamai purge --section default invalidate --production --cpcode 381644
I get the following error:
Purging...... [FAIL]
API Error: 400 400 Bad Request Invalid timestamp More Info https://problems.luna.akamaiapis.net/-/pep-authn/request-error
I have tried going to https://problems.luna.akamaiapis.net/-/pep-authn/request-error but that page does not seem to exist anymore. I am not sure what to do to get this working properly. If anyone has recommendations I'd love to hear about them as I do not know how to proceed to troubleshoot this issue.
Thanks in advance,
Nicola
It would nice to try to flush the DNS cache first.
https://community.akamai.com/customers/s/question/0D54R00007EhoqNSAR/akamai-fast-purge-api-giving-invalid-timestamp-despite-efforts-to-synchronize-time?language=en_US
Related
i have installed a fresh version of vscode in my new Manjaro installation.
Connection to the internet is active but i get the following error
"We cannot connect to the Extension Marketplace at this time, please
try again later."
When i open the developer console i get the following Errors:
Access to XMLHttpRequest at 'https://open-vsx.org/vscode/gallery/extensionquery' from origin 'vscode-file://vscode-app' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
workbench.desktop.main.js:2835 Error querying extensions gallery XHR failed
workbench.desktop.main.js:76 POST https://open-vsx.org/vscode/gallery/extensionquery net::ERR_FAILED
Can anyone help ;-(
What does that mean and how can i fix it?
Best wishes
Daniel
I have installed VS Code via the Manjaro Repository. But now i have tried installing via Snapcraft and this works ;-)
https://snapcraft.io/install/code/manjaro
I am trying to achieve the multicloud architecture. My network has 2 peers, 1 orderer and a webclient. This network is in Azure. I am trying to add a peer from Google Cloud Platform to the channel of Azure. For this, I created a crypto-config for 3rd peer from Azure webclient. But in the crypto-config, I made the changes like peers in Azure have their own certificates while for the 3rd peer, I placed the newly created certificates. Now I can install, instantiate, invoke and do queries in the peers(1 and 2). And I can install the chaincodes in 3rd peer. But I am unable to instantiate the chaincodes.
Getting the following error: Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: Post http://unix.sock/containers/create?name=dev-(CORE_PEER_ID)-documentCC-1: dial unix /var/run/docker.sock: connect: permission denied
Can anyone guide me on this.
Note: All the peers, orderer, webclient are running in different vm(s)
#soundarya
It doesn’t matter how many places your solution is deployed
The problem is you are running docker by using sudo command try to add docker to sudo group
Below block will help you out
https://www.digitalocean.com/community/questions/how-to-fix-docker-got-permission-denied-while-trying-to-connect-to-the-docker-daemon-socket
To learn more concept about docker.sock
You can refer to my answer in another Can anyone explain docker.sock
I have successfully set up Restcom GMLC after going through some issues (Restcomm gmlc configuration issue no local SSN is present for primary Address) Now the link beween the GMLC and the STP is up.
When i open the jss7-management console i have the error on the screen
When i try a map ati request (curl -X POST 172.21.75.34:8080/restcomm/gmlc/rest?msisdn=237699947943 ) I get this error The server does not support the functionality needed to fulfill this request But when i try the same request with the dummy msisdn 19395550113 i have a response.
What i think i'm unable to perform a map ati request because of this error undefined service for RestComm GMLC v1.0.66, somehow a certain service is not started but i don't know which.
I am trying the learn OpenShift Origin, and was going through the Getting Started example. I did all steps prior to creating a new application that combines a builder image for Node.js. I can see I have configured the docker registry using oc adm registry.
But in the build logs I see an error as
Pushing image 172.30.134.94:5000/test/nodejs-ex:latest ...
Registry server Address:
Registry server User Name: serviceaccount
Registry server Email: serviceaccount#example.org
Registry server Password: <>
error: build error: Failed to push image: Get https://172.30.134.94:5000/v1/_ping: http: server gave HTTP response to HTTPS client
and the build fails.
What could be the possible issue. Is it some port I have not opened or something? I would really appreciate if someone can share some insight on this and on what I may be doing wrong to get things to work
Thanks
There was a fault in the setting up of insecure registries. Fixed it and things started working.
Following the guide at https://www.openshift.com/developers/download-cartridges i wanted to try installing the CDK to see what it brings to the table. Unfortunately, I was unable to install the cartridge because of the following error:
Unexpected error: CLIENT_ERROR: Download of 'http://cdk-claytondev.rhcloud.com/archive/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8/cdk.zip' exceeded Content-Length of 9728. Download aborted.
Execute rhc create-app cdk http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8 against a local installation of OpenShift Origin. Or try to create an App throught the web console (again on a local installation, both are untested on rhcloud).
Looks like this was an issue on OpenShift Online also, which got fixed, but is still an issue on OpenShift Origin. Here is the bugzilla ticket for this issue (https://bugzilla.redhat.com/show_bug.cgi?id=1017776), I suggest you add your email address to it to be notified as they make progress against fixing it.