DNS setup pointing at APE in AWS

[Phil Dickinson]

Hi,

I have a domain called beyondadze.com registered with SOME_ISP.

I have a Linux server instance (Ubuntu) on AWS which is running apache2 and APE. Here are the netstat results showing the ports they are configured and running on...

ubuntu@ip-172-31-27-184:/var/log$ sudo netstat -lpnt

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1129/sshd       

tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      5817/aped       

tcp6       0      0 :::80                   :::*                    LISTEN      5717/apache2    

tcp6       0      0 :::22                   :::*                    LISTEN      1129/sshd 

beyondadze.com correctly returns the apache home page on the AWS instance but ape.beyondadze.com:443 is not reachable giving DNS error ERR_NAME_NOT_RESOLVED.

The test script confirms this. A snippet from the end is shown here...

APE JSF Version 1.1

Running test : Contacting APE Server

Can't contact APE Server. Please check the your APE Server is running and the folowing url is pointing to your APE server : http://ape.beyondadze.com:443

Something went wrong. If you can't fix it by yourself post a message on the newsgroups with the output below or join our IRC channel

The AWS Security Group in force is configured to allow inbound traffic on :80, :22 and :443.

Instructions here (https://github.com/APE-Project/APE_Server/wiki/Configuration-DNS) have prompted me to try:

• Creating an AWS 'Hosted Zone' for ape.beyondadze.com mapped to the instance
  
• Creating a CNAME at SOME_ISP to map ape.beyondadze.com to the AWS instance at beyondadze.com
  
• Both of the above
  

...but something is clearly still not correct. Note that using a CNAME checker currently resolves "ape.beyondadze.com" to "beyondadze.com.beyondadze.com" which has to be incorrect. Any help or suggestions for troubleshooting gratefully accepted.

 

[Phil Dickinson]

More information on this...the apache virtual host config is set as:

Servername beyondadze.com

ServerAlias ape.beyondadze.co.uk

ServerAlias *.ape.beyondadze.com

[Pablo Tejada]

Hello,

Two things: the domain(s) for APE should not be in your apache config (http://1.ape.beyondadze.com) and i don't encourage you to use a project that has reached its end of life.

--
--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to ape-p...@googlegroups.com
To unsubscribe from this group, send email to
ape-project...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/

---
You received this message because you are subscribed to the Google Groups "APE Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ape-project...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Sincerely,

Pablo Tejada

From Mobile

[Phil Dickinson]

Pablo,

Thanks for the reply. It wasn't obvious to me that APE was end-of-life. Unless you have other suggestions I'll switch to Node.js instead and see how that works out.

Phil

On Tuesday, March 7, 2017 at 10:58:08 AM UTC, Phil Dickinson wrote:

[Lotfi LACHIHEB]

we have a big problems with APE on production... using nodejs or rabbitMQ is a good idea

--

--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to ape-p...@googlegroups.com
To unsubscribe from this group, send email to

ape-project+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/

---
You received this message because you are subscribed to the Google Groups "APE Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ape-project+unsubscribe@googlegroups.com.

[BM]

I am currently using APE on production and it works fine. To use SSL (port 443) you must use stunnel. Also don't forget to hookup ape settings through AWS Route 53 and making sure to have a wildcard cert for your ape domain.