Forum | Appery.io

Hi

This week has been tough, since your Update the service has been up and down behind the REST over third party services

I attach the images from testing over the REST in the development side, but as you can see on the standard TEST it works fine, we do retrive all info from the REST, when we use ECHO Responce the same, all works fine, but when we use the Html5 test solution we do not get the right responce, so it craches. Same if we export to any OS.

We do have this same issue with all my apps that are behind Siteground, they did a sniff and this is what they found out:

a href="mailto:conecti7@conecti.us" rel="nofollow"conecti7@conecti.us/a [~]# curl -I http://appery.io/app/mobile-frame?src...
[1] 12435
a href="mailto:conecti7@conecti.us" rel="nofollow"conecti7@conecti.us/a [~]# HTTP/1.1 200 OK
Server: nginx
Date: Tue, 30 Dec 2014 04:49:26 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 2893
Connection: keep-alive
X-Appery-Node-Name: apperyio3
Pragma: no-cache
Cache-Control: no-cache, no-store
Expires: Wed, 31 Dec 1969 16:00:00 PST
Set-Cookie: JSESSIONID=AuoEuOgqcuZA8YHQr4xD3EFI; Path=/app; HttpOnly

Note that the outgoing connections to ports 80 (http) and 443 (https) are allowed in the server's firewall. If yuor applicaiton needs to access the remote server on different port you need to tell us the exaxct port and the remote host's IP address or host name so that we can allow the connection in our firewall.

You must gave changed something that is not allowing the info to pass true.

Also the service has been Up and Down because it started working on Wednesday but yesterday afternoon stopped working again

http://appery.io/app/view/7b0802c3-7d...
u:luis
p:12345

Please Help

CEC

Now the service is up again

Didi you made something?

No. Cool that it works again. Thank you for update.
Let us know if anything else arises.

Hmmm It was not really working I left the ECHO ON ????

This is what the people from Siteground say

I have once again checked the connection from yuor account to the remote api at http://api.appery.io/rest/1/proxy/tun... and I see and error 301 Moved Permanently. Here are the logs:

Code:
conecti7@serv01 [~]# curl -I http://api.appery.io/rest/1/proxy/tun...
[1] 27305
conecti7@serv01 [~]# HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sun, 04 Jan 2015 02:00:32 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: http://appery.io?user=adrianec

I have also checked the server's logs and did not find any records indicating issues with our services. If you think that the issue is caused by our server's configuration please ask the remote provider which settings we need to change so that we can set them for you.

What changes do I nned to ask in order to make it work, FYI behind Godaddy I do not have any problem

Best

Hi Carlos,

Please give us your app public link and describe steps to reproduce this problem in your app.

Thanks & regards.

http://appery.io/app/view/7b0802c3-7d...
u:Estibens
p:123456

or
u:Luis
p:12345

also
http://ipark19.app.appery.io/LogIn.html

It has been up and down like a yoyo, yesterday it did work, now is down again

Please help!!!

Hi Carlos,

It seems your 3rd party api don't reply to the request.

For example you can change "url" for this login service with codehttp://httpbin.org/get/code to see all request parameters. This is just echo service. And this service works correctly instead of yours.

I guess it could be some issue with your service brandmauer please check it.

Regards.

wow

The thing is that it was working smooth and I do have another 3 apps that do have the same problem

We simply cant log in, and it does work one day and the other do not

Also this only happens with Siteground hosting service because Godaddy hosting is working smooth so I need from you to tell me what ports does your new proxy use or what to instruct the people from Siteground to do

Again everything stopped working after the 25th, and it has been up and down, before that the REST services did not have any problem at all

Carlos,

Port depends only on your URL. So if you use HTTP - it 80, and if you use HTTPS it - 443, if other not specified directly in the URL.

I guess you can check brandmauer only on blocked/enabled ip adresses.

Regards.