Can someone give me the details for Port 80/443 and the Podio API

Answered

Follow

Bruce Keintz

• May 08, 2015 15:48

We develop on a Windows 2003 server that has IIS running and we have a test site with all our applications running on it. Naturally it runs off port 80. So when I run my new ASPX page from Visual Studio (VS) and the VS Virtual Development server fires up it picks a random port. When I authenticate to the API using App authentication it fails. I assume this is b/c of the port 80 issue. I have put the test server URL into the API key on the podio site, tried using just the external IP address for the box. No dice. Tried deploying the code to the local IIS and hitting the page through the website and still not working right.

So I need some insight to the port 80 process and how to get the communication through to my ASPX page. Our site does have it's own authentication so could that be the issue? Once I login and navigate to the ASPX page it is behind the public facing page.

0

• 

  Bruce Keintz

  • May 08, 2015 16:13

  Also when I run the site from my local machine it authenticates fine so my assumption is I need something more on the test server but not sure what. Any insite would be helpful.

  0

  Comment actions Permalink
• 

  Stefan Ukena

  • May 08, 2015 17:47

  Hi Bruce,

  I don't think your issue is related to ports. I use a local development server running on port 8080 all the time without any issue.

  Only Podio webhooks are restricted to accept ports 80 and 443, but your problem is related to authentication, so don't worry about that.

  You say that authentication fails, what's the exact error message that you are seeing?

  Best,
  Stefan

  http://www.diekollaborateure.com/go/podio/help

  0

  Comment actions Permalink
• 

  Bruce Keintz

  • May 11, 2015 15:56

  Stefan,
  Thanks for replying. I am getting a "object not set to instance of object error" when it hits the line podio.AuthenticateWithApp(appid,appsecret);

  I do not have this issue when running the project from my local machine. It seems to me that when I run this from our test development 2003 server that there must be some kind of communication issue when it try's to communicate with the API during the call with the clientID and clientSecret.

  I need to find a way to determine if this is the issue and how to overcome it.

  Thanks.

  0

  Comment actions Permalink
• 

  Stefan Ukena

  • May 12, 2015 20:12

  Hi Bruce,

  I think you will need to figure out how you can run a debugger on the machine you are having trouble with. Maybe a library is not installed, maybe a firewall blocks a port (though I would assume that ASPX would give you a different error message in that case). -- I don't develop in VS or ASPX, so I can only suggest a Google search for that: https://www.google.de/search?q=howto+debug+aspx&oq=howto+debug+aspx&aqs=chrome..69i57.2807j0j7&sourceid=chrome&es_sm=119&ie=UTF-8

  Hope this helps! Remember to post your solution, in case you can solve the issue.

  Best,
  Stefan

  0

  Comment actions Permalink
• 

  Bruce Keintz

  • May 12, 2015 20:16

  Stefan, thanks for your input. my solution was to attempt on our 2008 dev server and it worked without issue. Must be some limitation on the 2003 server that I cannot seem to find. So issue solved. I just wont use the old 2003 server.

  1

  Comment actions Permalink

Please sign in to leave a comment.