The website I want to test shows "no internet connection" ONLY while recording through jmeter test script recorder. Normally the website works fine but as soon as I click on start recording, a pop up comes up that says "no internet connection". I have recorded scripts on other sites using jmeter and it works fine. This issue comes up ONLY for this particular site I am testing. Could you please help me find out why is it happening? PL. refer attached images.
Image 1 - when jmeter proxy set and recording begins
Image 2 - normally website opens without any proxy/jmeter recording
It might be the case you're using the proxy server in your browser for connecting to the Internet.
And when you substitute the proxy server which gives you the Internet access with JMeter's proxy - you will be able to access local resources only.
The solution would be making JMeter aware of the upstream proxy server by providing the proxy details via command-line arguments like:
jmeter -H my.proxy.server -P 8000
These changes can also be made permanent if you put the following lines to system.properties file:
http.proxyHost=my.proxy.server
http.proxyPort=8080
https.proxyHost=my.proxy.server
https.proxyPort=8080
Related
Part of my development process involves using Mocha and Chai tests. I have a page in my test folder that loads all the code and tests, and I can start up a local node script that runs a simple local server, visit that page on http://localhost:8080/blahblahblah.html, and see the test results.
GitHub recently announced Codespaces and I signed up for the beta. If I start developing in a Codespace, I know there's a terminal there. If I run my testing server in that Codespace, how would I see the test results? Is it even possible to connect to the server in the container from outside? What would replace the URL I show above?
Found the answer here:
https://docs.github.com/en/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
It's actually pretty surprising. You just have your web server app print a localhost URL to the console, and the Codespace automatically converts that to a clickable URL with the appropriate port-forwarding. Kind of a huge surprise, but also pretty cool.
Just tested and this works.
When an application running inside a codespace outputs a port to the console, Codespaces detects the localhost URL pattern and automatically forwards those ports. You can click on the URL in the terminal to open it in a browser. For example, if an application outputs http://127.0.0.1:3000 or http://localhost:3000 to the console, the log would automatically convert the output to a clickable URL for port 3000.
When using the browser-widget of Livecode I have the following problems:
as target URL I use "www.tagesschau.de" and when I select the live stream I get the following message:
"Running this clip needs Flash-Plug-in up from Version 10.2"
The other error mess is:
"this video cannot be shown, due to Geoblocking it can accessed only from germany"
This means that browser shows up in the URL with a different IP than mine in the router. On my host-system everything works well. How can this happen without VPN?
Perhaps the properties of browser can be changed somewhere in the livecode-system. Where to put in the Flash-plugin and where to correct the IP?
Who can help? I need this functionality!
Thanks
I have published my website in IIS. The url is http://localhost/MyDemo. I want to give this url for testing to other people (anyone). How can I do that?
I tried to give sharing permission to "Everyone" in the Edit Permission.
Please help.
There are standard port forwarding tools that allow you to do this.
A helpful link here - https://www.sitepoint.com/accessing-localhost-from-anywhere/
Now ngRok is a tool I have used many a times. Its usage is pretty straightforward.
It can be downloaded from here - https://ngrok.com/download
Once ngRok is downloaded, you have to open the ngrok.exe, and it opens a console window.
Execute the following command
ngrok http 4983 -host-header="localhost:4983"
Here 4983 is a port number, in case you have one.
Once the command is executed the tool opens up a Url, which is accessible from anywhere. The below image is your Url, and it will be valid for a certain duration of time (if you are using the tool for free).
I got an Amazon ec2 server and when I go to the URL (Public DNS (IPv4)) in my browser I get "ERR_CONNECTION_TIMED_OUT"
I did the tutorial "Installing a LAMP Web Server on Amazon Linux" http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-LAMP.html
But got stuck on "If you are unable to see the Apache test page, check that the security group you are using contains a rule to allow HTTP (port 80) traffic."
I checked the security groups and they both set to "All traffic
All
All
sg-7496280c (default)"
And I still can't see the test page. I've also tried using the public IP address and I get the same thing.
There were no errors when installing packages.
I am able to connect using winSCP and upload html files but it doesn't serve them.
I don't know if I'm doing the right tutorial, or if I need to do other things first, or which tutorials apply to which types of servers or if ec2 and aws are the same thing or not etc.
I tried contacting support but it said I don't get technical support for basic accounts. I tried posting this on Amazon forums but it said something like "you can't post new threads right now, try again later"
I'm only doing any of this because you can't run node.js on hostgator.
ERR_CONNECTION_TIMED_OUT only happen either your apache not running or your server or your server is redirecting too much
Just I am unsure where you uploaded your HTML file and with what permission.
Do the basic thing reinstall only apache first.
check in your inbound and outbound port in aws security group in aws dashboard
if 80 port is open with anywhere option
check for
security rule
See if apache default page come. then upload your file.
can you tell in what directory you uploaded all your HTML
"ERR_CONNECTION_TIMED_OUT" can also be happen if you have not properly configure security group while creating the EC2 instance as it allows specific traffic to reach your instance.
If you want to set up a web server and allow Internet traffic to reach your instance, add rules that allow unrestricted access to the HTTP and HTTPS ports.
and copy Public IPV4 and use to visit the webpage rather than copying the url.
I am node newbie. I have a windows server, where I am running node.js with webserver.js. Start the node with webserver.js. Fireup the IE and when I tried localhost:port/index.html, the page shows properly in the IE. Now if I change the localhost to servername:port/index.html, IE is unable to display the page ('IE cannot display the webpage with you can try diagnose connection problem). Is there anything I need to enable in node so it is available outside localhost? I have jenkins runs on the same server, I did not do anything and it shows up properly with the server name. Just curious.
Thanks
my problem was that, I used the code from the link, in the link it was use IP address, I changed it to server name, now I am able to hit the link using both server and proper url. Hope this might help others. I did not change to use netstat though.