I am trying to launch a Matillion ETL instance through AWS and keep getting the error below
ERROR: This site can’t be reached amazonaws.com took too long to respond ec2-34-226-233-122.compute-1.amazonaws.com
This is the youtube video I follow. https://www.youtube.com/watch?v=piL4THHpxxY&t=254s
Everything works perfectly. I created the stack just as the lady in the video did (I even created my own keypair and everything. I did not use the same primary subnet and security group as the lady in the video though as she blurs hers out. I believe this might be the problem but as I am very new to AWS I am not sure.
Here are pictures of my stack info. When I click on the link in the third picture I receive the error message I posted above. I did not include the parameters field picture but if anyone thinks they need it to help I can include it just let me know.
Any help is much appreciated!
Agreed with your initial analysis, it's most likely related to your choice of Security Group (i.e. firewall), made around 5m28s into the video.
First of all, I strongly recommend you use https:// rather than http:// as the video shows.
Then you will need to make sure your new Matillion instance allows inbound network access for HTTPS (port 443) from your own IP address.
To do this in the AWS console, start at the EC2 service page
Make sure you are in the correct Region (use the dropdown top right)
Go to Security Groups under Network & Security.
Click into the Security Group you chose while launching the stack
Find the Inbound rules section, and press the Edit Inbound Rules button
If you don't see any line that already permits you access, then you'll need to add a new inbound rule
Press the Add Rule button
Choose HTTPS and set the Source to "My IP". It will automatically fill in your own IP address
Press the Save Rules button
The change should take effect immediately, and you should be able to reach your Matillion instance at https://...amazonaws.com using a web browser.
A couple of final pointers:
Your browser will likely complain about the security risk of an unknown TLS certificate. It's safe to click through this and proceed to the site because you know it's your own Matillion server
Whenever your own IP address changes - which might happen every few days depending on your internet provider - then you'll have to grant yourself access again from your new IP address
Related
I am from Iran. All Mtproto proxies have been banned by the GWF (the great firewall) and It's impossible to use them, although somehow someone made a weird Mtproto proxy with even weirder server name!
The Server name: cloudflare.com.nokia.com.co.uk.do_yo.want_to.clash_with.this.www.microsoft.com.there_is_no.place_like.localhost.www.bing.com.count_with_me.cyou.com.now_sudo.rm_rf.ddns.net.we_are_here.again_to_fight.everyone.i_am.the_internet.special_nbvd.koromozom.cfd.
It is the only way that we can access Telegram. Does anyone know how to make such proxies with this kind of Domain?
enter image description here
As you can see on the attached image, It is written unknown in the server name box, but when you connect to the proxy, you will see the following domain name.
Please help to create such proxies. I really need this.
We have two sites setup using the same API Key for uploading videos, one is the public server, another is on my local machine.
Even though they both use exactly the same credentials, the one on the public server is not working anymore (we're using https://github.com/laplacesdemon/django-youtube), throwing an error that credentials are incorrect.
Weirdly, I don't know where can be the problem.
There was one thing on our server, though, we changed the location so the IP address has changed.
Might it be this?
The IP list on the Server Key settings on Google Console is empty, and on the APIs requests graph I can see requests but can't find any log associated with them or something like this to see what's wrong.
Anyway, I guess the access is somehow blocked and there is no way to unblock it.
If anyone experiencing same issue, just create a new YouTube account! The only way of solving it, apparently.
Here is what I'm sure is a dumb question but I cannot find an answer for.
I purchased a domain name from 1and1 WITHOUT any hosting. I was intending to set it up on my own server which fell through, so I decided that I was just gonna do traditional hosting.
I found a great deal and promotion at Dreamhost for a year of hosting, so I signed up for the hosting service.
Through the 1and1 control panel, I have redirected to the Dreamhost name servers, but I'm not really sure what to do next.
How do I now upload my website files to Dreamhost and load them when visiting the domain that I purchased from 1and1?
I understand this may be vague, and I apologize if so, just want some guidance. Let me know if there is any information I can give to help.
Purchasing your domain through 1and1 is no problem. I'm not extremely familiar with either company or their infrastructure but I can give you a general guideline with an attempt to tailor it to your needs. Hopefully you'll find this helpful.
First step I would personally take would be to update your nameservers at 1and1 to use Dreamhost's. If they are using cpanel, this may be a requirement. Regardless of their control panel, this will likely be the easiest way to manage any updates you need to make. After this you will only need to login to 1and1 to renew your domain or transfer it.
To change your name servers:
1) Log in to the 1&1 Control Panel using your Customer ID OR domain name and your password.
2) Click the Domains link from the Domains & Webspace panel.
3) Check the box next to the domain to select it and click Show DNS Settings from the DNS drop-down box above the list of domains.
4) Click the Edit button next to Name Server Settings.
5) If you are currently using a CNAME with the domain, you will not be able to set which name servers should be used with the domain unless you select DNS from General settings.
Select My name server from the Name server drop-down box.
6) Enter the first name server address into the Primary name server text box.
Select My secondary name server from the Secondary name server drop-down box to add a second address.
Enter the second name server address into the 1st secondary name server text box.
You may add a third and fourth name server address if necessary, but only two are required.
Click the OK button to save your settings.
For step 6, you should be entering the following name servers (unless Dreamhost has provided different servers when you opened your account): ns1.dreamhost.com, ns2.dreamhost.com, ns3.dreamhost.com
Note: you may only be able to enter two of the three listed.
Next you need to login to your Dreamhost control panel for hosting. Ensure you have your domain added. If not, go to Manage Domains and add your domain. It should provide instructions for adding your domain. If you plan to have everything hosted at Dreamhost (as it sounds to me like you do) but sure to selected "Fully Hosted." You can manager your DNS through their domain manager once you are using their nameservers. You can add A records if needed to point to your IP but generally in shared hosting environments, the control panel will perform the basic configuration of the A records for your site.
As always with DNS, it may take some time for your changes to propagate. You may want to flush your dns as well (on your local machine).
edit: Sorry I just re-read your question and realized you accomplished what I answered. Here's some additional steps to get your website up and running:
Are you using a static HTML website? If you are using Wordpress or another CMS/Application, please let me know as the instructions will vary for those types of installs.
If it is a static website, download an FTP Client, if you do not have one already. My personal recommendation is FileZilla, simply because it is free and easy to use but any FTP Client will work. Log back into your DreamHost control panel and look for your server information under "Account Status." It will say "Your Web Server:" followed by the name of the server your account is on. Enter that server name into FileZilla for the IP/Host. Try using your controlpanel login and password and the port would be 21 for standard FTP. If your login does not work, go back to your control panel and look for an option called "FTP Accounts." Go into this section and create a new FTP account. Now use that account for your user and password in FileZilla. This should normally drop you into your website's home folder. If not, look for anything such as "html", "public_html", "www" and upload your files there. Ensure you have an index.html or index.php file.
If you have any additional questions, please let me know and I can update my response to address them.
In order for your site to show up from the Dreamhost hosting, you will need to set the A-record in your DNS at 1and1 to resolve to the IP address that is provided by Dreamhost. Making changes to your 1and1 DNS is not part of my expertise (I work at Dyn), but if you have any trouble, their support team should be able to assist.
Good luck!
CL
I'm sorry if this is not a programmatic issue, i also may get many down votes for it, but i really need to know in details, what does (Resolving Host) means ?!
I'm trying to configure a connection to a web server hosting a friend's web site, and i'm developing a vb6.0 app. using WinSock.OCX tool, and one of its states is (Resolving Host) so i need to know what does it mean to be able to provide some code for it.
You don't have to handle that state. This is just the phase when WinSock.ocx is converting a DNS name (let's say www.dilbert.com) to the corresponding IP (184.106.169.31). This is handled automatically by WinSock, so you just have to wait.
WinSock might give you errors during this phase, because it could be that
the supplied domain name is/was no longer valid
the supplied domain name is invalid (92$!#d.com, for example)
the DNS server is not available (no network connection, for example)
I have a site i am working on that i would like to display only to a few others for now. Is there anything wrong with setting up windows user names and using windows auth to prompt the user before getting into the development site?
There are several ways, with varying degrees of security:
Don't put it on the internet - put it on a private network, and use a VPN to access it
Restrict access with HTTP authentication (as you suggest). The downside to this is it can interfere with the actual site, if you are using HTTP auth, or some other type of authentication as part of the application.
Restrict access based on remote IP. Just allow the IPs of users you want to be able to access it.
Use a custom hostname. Have it on a public IP, but don't publish the hostname. This means make an entry in your HOSTS file (or configure your own DNS server, if possible) so that "blah.mysite.com" goes to the site, but that is not available on the internet. Obviously you'd only make the site accessible when using that hostname (and not the IP).
That depends on what you mean by "best": for example, do you mean "easiest" or "most secure"?
The best way might be to have it on a private network, which you attach to via VPN.
I do this frequently. I use Hamachi to allow them to access my dev box so they can see whats going on. they have access to it when they want , and/or when I allow. When they are done I evict them from my Hamachi network and change the password.
Hamachi is a software VPN. Heres a link to Hamachi - AKA LogMeIn
Hamachi
They have a free version which works quite well.
Of course, there's nothing wrong with Windows auth. There are couple of (not too big) drawbacks, though:
your website auth scheme is different from the final product.
you are giving them more access to the box they really need.
you automatically reimaging the machine and redeploying the website is more complex, as you have to automate the windows account creation.
I would suggest two alternatives:
to do whatever auth you plan on doing in the final website and make sure all pager require auth
do a token cookie based auth - send them a link that sets a particular token in a cookie and in your website code add quick check for that token before you even go to the regular user auth
If you aren't married to IIS, and you need developers to be able to change the content, I would consider Apache + SSL + WebDav (aka Web Folders). This will allow you to offer a secure sandbox where developers can change and view the content without having user accounts on the server.
This setup requires some knowledge of Apache so it only makes sense if you are already using Apache or if you frequently need to provide outsiders access to your web server.
First useful link I found on the topic: http://pascal.thivent.name/2007/08/howto-setup-apache-224-webdav-under.html
Why don't you just set up an NTFS user and assign it to the website (and remove anonymous access)