• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problem setting up plesk panel on AWS EC2 instance.

AkiraD

New Pleskian
Dear friends,

I have been problems with my plesk panel and I'll apreciate some help.

I followed this step by step http://kb.parallels.com/114947 and choosed the BYOL.
I added a new network interface and I have 2 public IPs (to create ns1 and ns2) an 2 private IPs.
Plesk recognized all the interfaces.
I created the first customer, edited DNS template and I created 2 A entries: ns1.mydomain.com.br with Public IP1 and ns2.mydomain.com.br with public IP2.
First of all, I opened all the ports that I saw in documentation... was a lot, but I did. I did it on Windows firewall and AWS security group firewall.
I wanst able to ping or something... An when I go to direct my domain on domain reseller, I recieve the message: DNS SERVER MASTER: TIMEUOT, DNS SERVER SLAVE: TIMEUOT.
Well to test conectivity, I opend all TCP/ICMP ports and I was able to ping, but my error on reseller is the same.
Anyone can help me? I really don't now what could it be...
I did it many times on softlayer, but is my debut in AWS. I don't want to use Route 53 as a DNS.

Thank you


Akira
 
I recieve the message: DNS SERVER MASTER: TIMEUOT, DNS SERVER SLAVE: TIMEUOT.
Where exactly you see this error? Could you please provide more details, screenshots, steps-to-reproduce?
Do you have problems with other services on these public IP addresses? Or it is occurs only for DNS?
 
what do the commands show:
>nslookup ns1.mydomain.com.br <your public IP1>
from outside of the instance and:
>nslookup ns1.mydomain.com.br <your private IP1>
from inside of the instance?
 
Where exactly you see this error? Could you please provide more details, screenshots, steps-to-reproduce?
Do you have problems with other services on these public IP addresses? Or it is occurs only for DNS?

In Brazil, we by domains in registro.br.
When you pay a host, you need to point S server on registro.br.

I recieve the error at this time.


timeout.jpg

I can ping normally,.... wait...

I've tried now and... gone...

Thank you guys for the help!

Best regards...
 
Are you sure that bind is started on these nameservers and port 53 is not firewalled? I can ping them but I can't connect to port 53:

$ telnet ns1.myprojekt.com.br 53
Trying 54.213.106.148...
 
Igor, can I ask you 2 things her or I have to crate new thread?
I will ask, if you its wrong, I'll create new thread...

1 - how can I access the adm profile FTP? I made my default site as a subscriber (admin), and now I cannot acces FTP. I always receive a 530 error (home directory is not acessible). Another sistes is working fine, only the subscriber don't works...
2 - how can I made my aws url without https? Or how can I avoid this screen???

ssl.png

Thanks
 
Last edited:
Back
Top