I tried
curl -F "file=#/mnt/usb/anime.txt" https://dbinbox.com/galihpa
but it gave me
curl: (51) Cert verify failed: BADCERT_NOT_TRUSTED
I just can't figure out what's wrong. The url I want to post to is https://dbinbox.com/galihpa
Please help me..
I'm the creator of DBinbox :D
Unfortunately the old API has become depreciated with the recent total rewrite, deployed September 1st. There is currently no predictable way to upload files to DBinbox with curl.
That said, I'm working on a much prettier API that would make this a lot easier. I'll update this answer with documentation when it's ready!
Related
I am trying to setup a WhatsApp bot using voiceflow, based on the tutorial found here. I've set this up before and everything has worked fine, but now I can't seem to configure the webhook.
The steps I'm performing are as follows:
Clone the repo here
Checked ngrok is installed (version 3.0.7), and its location (/usr/local/bin/ngrok)
Created a .env file at the root with the VERIFY_TOKEN, PORT, and WHATSAPP_TOKEN
Started the app from root with npm start
Started ngrok with ngrok http 8000 (the same port as specified in my .env)
Checked the resulting address works in the browser
According to the documentation, I then configure the webhook by adding "/webhook" to the end of the URL, and adding the same VERIFY_TOKEN as specified in my .env file. This, however, gives me the following error:
The callback URL or verify token couldn't be validated.
Please verify the provided information or try again later.
I've had a look around at similar questions here, but could not find what was wrong. I have also spoken to others who encountered similar issues over the last few weeks. This process was working up until recently (Nov 2022).
The error msg: The callback URL or verify token couldn't be validated. Please verify the provided information or try again later. usually means you are not returning a 200 response to the webhook origin. I would make sure your code is returning a 200 to whatsapp.
As an alternative, try to set the webhook on glitch as explained here:
https://developers.facebook.com/docs/whatsapp/sample-app-endpoints#cloud-api-sample-app-endpoint
so that you can check if your meta account is valid.
From what I have found it seems that feature is now behind a paywall. It worked fine a few months ago on the free tier of ngrok. So you will need to upgrade your ngrok subscription for WhatsApp to start validating. You can read about it here. Try using Cloudflare tunnel.
I have an issue on my script where I run the script and it gives me this error:
enter image description here
Given that error, I tried to add this web_set_user on my script and still not working.
enter image description here
Also other than that, when I check the replay, it shows this error:
enter image description here
I tried configuring everything from IE browser to Loadrunner but still no luck.
SAPNego: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/tsec_SPNEGO_configweb_new.html
Web_set_user: Authentication required, please use "web_set_user" solution not working
Would anyone please help me if you did encounter this issues?
Run time browser is not a full featured browser. I would not expect it to render a modern framework correctly
Make sure wininet is elected with web_set_user()
Have you considered Truclient?
This is already resolved. We just add a header which is a cookie and it works fine now. Thank you.
I am trying to use wget to download a pdf from my university website
the url looks something like this :
https://online.myuni.ac.uk/webapps/blackboard/execute/content/file?cmd=view&content_id=_xxxxxxx_1&course_id=_xxxxx_1
I have tried using wget with both cookies and also with --user=xxx --password=xxx
However what it downloads is a html page showing me a log-in screen saying I have insufficient permission.
I cannot get this to work, and I am not sure how to proceed. I am very inexperienced with linux and programming in general any help is appreciated.
I finally got this working by exporting cookies from a browser, but the key was to include the "keep-session-cookies" parameter.
The basic work-flow I am trying to implement is to generate a PDF from FileMaker data, upload it to DocuSign for signing, and download the signed document back to FileMaker.
The DocuSign API requires custom headers, so I cannot use the built-in FileMaker 13 Insert From URL script step. Instead, I am using the BaseElements plug-in BE_HTTP_Set_Custom_Header and BE_GetURL functions. I currently have the DocuSign Login API call working.
Now I am trying to use the DocuSign API to upload a document and request a signature. This requires a multi-part/form-data POST request. Unfortunately, neither the BaseElements nor Troi URL plug-ins support multipart/form-data. In fact, I cannot find any plug-in that does. Is anyone aware of a FileMaker plug-in that supports multipart/form-data POST?
https://www.docusign.com/developer-center/quick-start/request-signatures
According to a comment on the Goya support forum last week, the next version of the BaseElements plug-in should support pass-through to the curl command line utility. If true, then as an alternative it seems possible to write a curl command to build the proper request, but my HTTP and curl knowledge is limited. So far, I have been unable to get the DocuSign signature request example working in Terminal. Has anyone been able to upload a document and request a signature with a single curl command?
http://support.goya.com.au/discussions/free-baseelements-plugin/1088-be-plugin-and-http-file-upload
Finally, I would be grateful for any other ideas or suggestions for attacking this problem.
Thank you!
Yoo could use ScriptMaster and Groovy to write your own function to support the multipart/form-data type
It took me a whole week but I managed to get it working on FileMaker 14.
It took me a whole week but I did manage to integrate it completely. I studied with my CEO the various providers out there and we ended up choosing DocuSign because our clients would be able to sign/approve our Estimates from literally any device (and also providing us with some more information if we need) such as Credit Card and etc), and because the annual costs were very competitive.
On the Development side it was hard, but not impossible.
The steps to master it are as follows:
1 - Study REST, and HTTP requests fundamentals (two youtube videos will do the trick).
2 - Get familiar with the command Curl in order to make POST and GET requests from Terminal (on Mac). Once you get to this point. Then you can try to follow Docusign's steps to POST and GET from Mac Terminal (not through FileMaker as yet). The first command that worked for me is as follows:
curl -i -H "Accept: application/json" -H 'X-DocuSign-Authentication:{"Username": "myemail#hotmail.com","Password": "mypassword", "IntegratorKey": "fae5e715-dec2-477f-906e-b6300bc9d09a"}' -X GET https://demo.docusign.net/restapi/v2/accounts/8aabdb38-41ab-4fab-bae9-63a071394a7a
If you replace the text above in bold with your DocuSign Developer credentials/information you should get a HTTP Header 200 OK - which means that you are in the right way.
This is important because you need to understand what information should be in the Headers, allowing Docusign to accept your requests.
3 - Translate the same concept into FileMaker. This is the most tricky part. First you need to create two Custom Variables. One will be your Docusign authentication (email, password and Integration Key). Something like this:
enter image description here
and the other one will be your endPoint , which is simply your Docusign url followed by your account number.
enter image description here
4 - Now you need to install BaseElements plugin onto your FileMaker Database(you wouldn't need this if you were using FileMaker 16). This will allow you to send POST, GET, DELETE, and UPDATE requests to Docusign. Unfortunately BaseElements's documentation is not super so I struggled a little bit till a get an actual result, but I will try to break it down for you here.
In order to make a GET request similar to the example that we have made we need to make a one line Script which looks like:
enter image description here
and then, inside the Refresh Object function:
enter image description here
This Script was adapted from a BaseElements plugin used to do Vimeo HTTP GET Requests - please see the link for more details on how to use it and test it: FileMaker REST using BaseElements Plugin - ISO FileMaker Magazine .
I think this gives you pretty much a good idea of how it works.
Unfortunately Docusign still doesn't provide any documentation or support to FileMaker developers, and this is as far as the internet goes. So if you need to make POST requests, it will get a bit more complex since you will have to put your FileMaker fields in JSON format, BaseElements POST syntax changing the script from GET to POST accordingly and POST inserting one more command with your data:
// insert this on your FileMaker POST script after the Headers List end
~data = BE_HTTP_POST ( ~endpoint ; "{
\"documents\": [
{ all of your JSON code adapted to FileMaker }]}");
You will also have to turn the PDF files that you want to send into Base64 format.
If you do this trick you will be good to go.
I've been trying to work with my Nest thermostat so I can work it into home automation run by my Arduino-based projects. So far, I've completely failed to get anything done. I would greatly appreciate input or redirection to other resources.
I signed up under the Nest developer and created a client with read/write permissions.
I'm at the OAuth step where I want to start pulling basic information out of thermostat. I went to https://home.nest.com/login/oauth2?client_id=[clientID]&state=STATE where clientID is the clientID for my project. I left STATE as is.
I received the PIN that I'll call 99ITPUMP and I put that into Git BASH like so:
curl POST https://api.home.nest.com/oauth2/access_token?code=99ITPUMP&client_id=[clientID]&client_secret=[clientSecret]&grant_type=authorization_code
The response I get is
$ curl: (6) Could not resolve host: POST
{"url":"/oauth2/access_token?code=99ITPUMP","message":"404 Not Found"}
I've tried getting a new auth code multiple times and still can't get anything. Can anybody tell me what I'm doing wrong? I need to get basic information from my Nest within the bash console. For anyone providing an answer, please make it is idiot-proof as possible. I really have no idea what I'm doing so I'm doing my best to learn.
Try something like:
curl --data 'code=99ITPUMP&client_id=[clientID]&client_secret=[clientSecret]&grant_type=authorization_code' https://api.home.nest.com/oauth2/access_token