Tag Info

New answers tagged

1

I had a similar issue but I was able to solve it by modifying the routing. I had to add these routes in my /etc/networking/interfaces file: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp post-up ip route add default via g.g.g.g dev eth0 tab 1 post-up ip rule add from x1.x1.x1.x1/32 tab 1 priority 500 auto eth1 iface eth1 inet dhcp post-up ip ...


2

There is a limitation as to changing instance sizes within EC2, this is to do with the virtualisation type (PV or HVM) the generation of VM (some of the older instance types such as t1.micro cannot be resized to newer instance types such as t2.micro). As long as the instances are using the same virtualisation type then you can change the size between any of ...


0

You should use either Security Groups or iptables - I advise you against using both at the same time. It makes administration more complex, error-prone and you'll often find your self in situation where things you expect to be working are having problems. So, in short, turn of iptables: chkconfig iptables off service iptables stop


0

You have 2 options to fix the problem. 1) Assign 2 IPs to eth0(it is possible from ec2 console), you will need to use "ip addr add ..." to configure the second IP. 2) Configure source based routing. Possible answer: http://superuser.com/questions/638044/source-based-policy-routing-nat-dnat-snat-aka-multi-wans-on-centos-5


1

The previous answer is not 100% accurate. What back-end authentication ACTUALLY does is ensure that the public-key your backend server reports (when ELB is talking to your server over HTTPS/SSL) matches a public key you provide. This would prevent somebody from attaching a malicious server to your ELB, or mitigate somebody hijacking the traffic between ELB ...


0

Fixed it. There were 2 core problems working in tandem which caused this.... Core problem 1: When looking at Ubuntu's /etc/hosts file, though I had no memory of ever editing it, the problem became apparent. The third line was routing to a non-existent server and I really wish I knew why. This third line was removed: 127.0.0.1 localhost 127.0.1.1 ...


2

Add a ServerName attribute in your VirtualHost config with the hostname you want to use.


2

It seems like your instance is failing to boot. Go to "Actions" -> "Instance Settings" -> "Get System Log" and see if you get any valid output there. There are a number of things that could be wrong, I usually test-reboot instances to make sure they'll come back up properly after running my configuration management tool (you do have one right?) before ...


0

Common issue, make sure that you Disable Source/Destination Check on the instance ( right click -> Networking -> Change Source Dest. Check ) You'll only need to do this on the Vyos box. You also don't really need a second interface. You could create a second subnet and on that route table for that subnet make the 0/0 route point to the Vyos instance if ...


3

There should be no charge for either of those things. It's a bit of a stretch to call them "resources." In the world of AWS, and in contrast to the other items on that list, those items are more like "metadata." (The same logic applies to Placement Groups.) You'll potentially need them if you launch future instances, but they aren't consuming anything ...


0

Don't individually add each EC2 instance's IP address to your inbound security group. Instead allow inbound traffic from the security group of the EC2 instances. Then any EC2 instance which uses that security group will be permitted access from the same rule. Generally speaking, auto-scaling groups are best used behind Elastic Load Balancers if outside ...


3

This means that a new inbound rule needs to be applied to the security group for RDS that allows this new EC2 instance to connect to RDS via port 5432 (postgresql). Rather than using public IPs for your security group rules, I suggest using private IPs. Run both EC2 and RDS in the same VPC, then allow the entire VPC subnet IP range containing your ...


-4

Erm..... First hit from google (search string mx record lookup) was: http://mxtoolbox.com/ For those who have never used it, it has a history button to show previous mx records for a given domain.


1

Might also be worth allowing HTTPS on port 443 as well: HTTP tcp 443 443 0.0.0.0/0


0

Try making the tunnel yourself with ssh -f -L 3306:localhost:3306 11.22.33.44 -N Then just connect to localhost:3306 without SSH encryption.


0

When I had that problem, it was because the host name used in the 'connection' part of you mysql client wasn't resolving properly its name in the MySQL's server to the server itself. Usually I had to change the /etc/hosts and add localhost to the 127.0.0.1 entry. Your case doesn't seem to be the same as you are using the ip 127.0.0.1?! BTW, have you ...


0

They are very guilty of not keeping these instances current. Thus the best thing to do is to create your own base image and install the ABBYY engine yourself. Also keep in mind that because OCR is a CPU and memory hog i've found the current instances they have created are not supporting a typical OCR load. I often think these instances are for marketing ...


0

The best way to debug an ELB issue is to do the following: Ensure the security groups on the instance(s) are setup to allow the incoming port (80) Make sure your health check is setup correctly tail -f (or similar) the logs of the instance(s) you're trying to add to the balancer. See that the ELB is correctly pinging the instance(s) An example ping ...


0

We have lot of possibilities to create or extend a DC to cloud. firstly, we have EC2 services to host a new AD or extend your AD to cloud. Please refer to the AWS directory services. AWS Directory Service Now you could also launch a windows server with AD service configured over a VPN connection(you can use direct connect or linux server VPN) to the ...


8

How would this be setup connection wise without forcing all traffic through the domain controller? With site to site VPNs. You'd set up your cloud assets as a site, and then establish a site-to-site VPN between your cloud site and each of your physical sites. An alternate option, that Microsoft uses, but is generally ill-advised (unless you really, ...


4

I noticed you're using the db.micro instance. As with EC2, the micro instances are designed to be budget-friendly, but at a cost of performance. That said, you'll get a much worse performance when loading these types of servers versus the normal instances because the CPU time is given to the instance "last" compared to other instances sharing the same ...


0

More than likely your disks are not yet correctly attached to your instance. When you add additional disk space to an EC2 instance, your disk isn't immediately mounted on your Linux. ITKBCentral has a blog post with a tutorial on how to move your running instance to a larger disk. If this isn't your current situation, please provide more information about ...


1

In order to use your own domain you need to setup a so called Hosted Zone in Route53 (which is an AWS service). You should then create a Record Set which you point against your obtained Elastic IP. Read more about it here (see step 3): http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingNewDNS.html If the link above does not give you all the ...


1

To resolve this issue: Remove the lines like: mysqlnd_ms.enable=1 mysqlnd_ms.force_config_usage=1 mysqlnd_ms.config_file=/etc/mysqlnd_ms_cfg.ini extension=mysqlnd_ms.so from the php.ini file Create a new file called /etc/php.d/mysqlnd_ms.ini and put those lines in there and restart php-fpm service php-fpm restart


0

Some versions of OpenSSL were broken in Ubuntu due to problems in OpenSSL, not Ubuntu itself and may have been broken in other distros as well, such as Amazon Linux, when connecting to an ancient server that can do no better than TLS 1.0 unless you explicitly force it, as @AndySmith was suggesting above (the openssl s_client -connect option to try to see it ...


0

when we attach a bootable volume to another Windows 2012 R2 instance, it marks that as non-bootable one as it already has a bootable volume. And when you re-attach it to original instance, your instance doesn't boot any more. So, there is a requirement to fix or re-build boot configuration data(BCD) for that volume. In order to fix this, perform below ...


2

I have done this, please read my article before you actually do this here: http://neonos.net/wp-admin/post.php?post=30 The functionality has been programmed by Amazon in Nov 2014, however it has not been implemented in the web based console, hopefully they will do this soon. There is also no documentation or any articles that I could find on this topic. ...


0

By default there is no internet access to the VPC . On your VPC dashboard click Route Tables then click Routes. Click Edit, then add the following information : 0.0.0.0/0 & InternetGateWayName. Click Save . That's it .


2

You forgot to create a file system. mkfs.ext4 /dev/md0 or something like that.


2

It appears that there's a firewall between the client and server that is blocking the communication required for the client to join the domain. My suggestion would be that if the firewall is relevant only to these two instances that you unblock (allow) all traffic through the firewall between these two instances.


1

According to: Amazon Web Services – Implementing Active Directory Domain Services in the AWS Cloud With an Amazon VPC, Dynamic Host Configuration Protocol (DHCP) services are provided by default for your instances. DHCP scopes do not need to be managed; they are created for the Amazon VPC subnets you define when you deploy your solution. These DHCP ...


2

It seems that the DNS record for the DC could not have been found. Have you tried adding the DC's IP to the preferred DNS servers under the computers IPv4 settings?


2

Launch doveconf -a | grep _valid_ You have to set that variables to something like that: first_valid_uid = 26 last_valid_uid = 0 first_valid_gid = 6 last_valid_gid = 0


2

We finally found the solution. You can fix the download speed by running on the NAT machine (as root): ethtool -K eth0 sg off This disables scatter-gather mode, which (as far as I understand this) stops offloading some network work on the network card itself. Disabling this option leads to higher CPU usage on the client as the CPU now has to do the work ...


0

Amazon announced support for Multi-AZ support for Redis on 2014-10-24, so this you can achieve through the AWS console. Regarding your other question about hosting your own EC2 instances with Redis, that is fully possible and will probably be cheaper. However, you will miss out on a lot of features (e.g. read replicas, automatic backups, detailed ...


0

If your machine is started and the auto-unlock feature is enabled then as long as you have a login to the machine then you can access the data on the bitlocker drive. Furthermore, there are utilities which erase the password allowing you to login without a password and access the data on the bitlocker drive. Basically Auto-Unlock defeats the purpose of ...


1

I also use NAT boxes in a similar setup in production so very interested in your findings. I haven't had similar findings before production, but maybes it's an issue that I haven't paid attention to before. Let's do some science! ============================================================================ Theory: NAT boxes can download and upload faster ...


0

The command is looking for a file that does not exist file does not exist: /var/www/html/certificate.pem Possibly your certificate is not named certificate.pem, or my guess is you don't have a folder named /var/www on your local system where you're running this command (nor on your mac). You need to put the location of certificate.pem on your local ...



Top 50 recent answers are included