Current time: 12-10-2019, 12:13 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Private Instance AWS still requires api key
11-22-2016, 08:25 AM
Post: #1
Private Instance AWS still requires api key
Hi everyone, fairly new to WPT.

I have setup an EC2 AMI and have been able to run tests both through UI and API.

I created an API KEY at https://www.webpagetest.org/getkey.php

that key has allowed me to run several tests but now that i am starting to run more tests i started receiving this response:

{
"statusCode": 400,
"statusText": "The test request will exceed the daily test limit for the given API key"
}

It sounds like i need to reconfigure my private instance so it is stand alone. been trying to find documentation for this but unsuccessful so far.

thanks
Find all posts by this user
Quote this message in a reply
11-23-2016, 11:56 PM (This post was last modified: 11-24-2016 12:54 AM by e14nielson.)
Post: #2
RE: Private Instance AWS still requires api key
my problem was that i was hitting the public URL not my private agent.

new issue:

now i have my EC2 instance autoscaling and working very very well through the interface. i still cannot drive it via command line/API

calling on the server :
webpagetest test https://www.yahoo.com/ -k <My_API_Key> -s "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/"

returns:
{
"statusCode": 200,
"statusText": "Ok",
"data": {
"testId": "161123_RN_1",
"ownerKey": "d2bd2078616a8e6393695733d33c02a64851e3bd",
"jsonUrl": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/jsonResult.php?test=161123_RN_1",
"xmlUrl": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/xmlResult/161123_RN_1/",
"userUrl": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/result/161123_RN_1/",
"summaryCSV": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/result/161123_RN_1/page_data.csv",
"detailCSV": "http://ec2-35-163-162-98.us-west-2.compute.amazonaws.com/result/161123_RN_1/requests.csv"
}

but when i try to find status : webpagetest status 161123_RN_1
{
"statusCode": 400,
"statusText": "Test not found",
"data": {
"statusCode": 400,
"statusText": "Test not found",
"id": "161123_RN_1"
}
}

Thanks,

Found my issue:

when calling for status --server is required for a private instance

This worked:

webpagetest status 161123_RN_1 -s "ec2-35-163-162-98.us-west-2.compute.amazonaws.com"
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)