I am running Apache2 server on Raspberry pi 2 running osmc (based on Debian jessie).
I am occasionally getting 400 bad request errors (both with Firefox and Chrome), with Nginx written at the bottom. According to some advices I have found I should edit nginx configuration file so it will be able to take larger header files.
But I don't have Nginx installed at all. Could you please help me figure this out? When I google for answers, all I get is related to Nginx configuration.
Related
i'm new to coding and right now i'm learning to launch json server through VSC in my bootcamp (flatiron). I'm having trouble with opening it in my localhost file in my google browser. I'm running Ubuntu on my PC. when I installed npm install -g json-server it stated that I have 4 moderate severity vulnerabilities.
I have tried to turn off my firewalls and antivirus, cleared the chrome history, tried to change my DNS and had no luck.
I've been stuck with this issue for 2 days now, please help !
[this is what local host is stating in the web browser1
This is the vulnerabilities being shown
I answered this below for anyone that is interested
I'm on Windows 10 using Chrome, Firefox and MS Edge. I'm trying to do something for a class I'm taking and can't get it to work. All I want to do is add something like this to the hosts file:
127.0.0.1 mysite.dev
This is ALL to run on my local PC. I eventually need to have my site able to run on IIS, but this is the first step and I can't get past it. (I'm on my second day trying)
What I've done:
I did edits in notepad on a file on my desktop.
I renamed the original hosts file in the drivers/etc directory.
I copied my file into the drivers/etc directory.
I ran ipconfig -flushdns
I successfully pinged the new site with: ping mysite.dev
I cleared browsing history in all three browsers.
I reopened all three browsers.
All that failed to make any difference (and I rebooted as well) So I added this:
I ran ipconfig -flushdns
Then ipconfig -renew
Then ipconfig -registerdns
Then repeated steps 5->6 and all failed to make any difference. These are the errors per browser:
Chrome: This site can’t be reached mysite.dev refused to connect.
Firefox: Unable to connect Firefox can’t establish a connection to the server at www.mysite.dev.
MS Edge: Hmmm...can’t reach this page
I noticed that all three browsers changed http to https. Not sure if that mattered but I followed instructions to disable this re-direct for all three browsers and NONE of them actually stopped the redirect to https.
And I still can't the correct result, which should be the IIS default page. I can see the IIS default page with localhost, so IIS is running.
Help! Any ideas or directions at all would be very appreciated!
Got the answer from someone. Google owns the .dev domains and has restrictions on it so it HAS to be HTTPS, which requires certs etc, which is not in the scope of my class. I just changed it to mysite.local and BOOM!, there it was! Thanks.
Recently I installed Gatling for performance testing on Ubuntu 14.04. And to run the recorder I needed to configure a proxy server in my browser. I tried to change proxy settings in Google chrome, but I don`t have rights. So I tried to do it using network settings in Ubuntu (Network -> Network proxy). But when I open a website which I need to test, nothing happens in the recorder.
So I do not really know is there a problem with the proxy server or Gatling itself? And how to check if the proxy server is configured correctly?
I would appreciate any help!
It's a bit too late, but I had a similar problem today. Was able to solve only by setting global IP address like xxx.xxx.xxx.xxx. Nor localhost nor 127.0.0.1 worked for me Chrome. After that I was able to notice http requests in Recorder inside Executed Events
Hopefully it could help somebody else
Edit : this is how setting looks like in Chrome, taking into account you have specified in Recorder Listening port to be 8000 also:
EDIT:
The localhost seem to be working fine in my firefox, IE and even Chrome's incognito mode. These is a problem specific to chrome. Any ideas?
PREVIOUS:
I just uninstalled VisualSVN Server from my Windows 7. But now when I try to hit localhost, I get redirected to localhost/svn. I am using WAMP and developing something that requires the root access. I can not put the project in a sub directory. I have also tried netstat -ao but no process is using ports 80 or 443.
You may have solved the problem....but for future, those who came here like me looking for a solution to this, this seems to be a prob for browser cache....clearing browser cache history solves the problem.....did for me...
If you uninstalled VisualSVN Server, then it's some other application which runs on 80 / 443 port that redirects you to /svn. Some steps that may help you to determine the root cause:
Verify that VisualSVN Server has been successfully uninstalled.
Start appwiz.cpl and see whether VisualSVN Server is listed as the installed application,
Start services.msc and see whether "VisualSVN Server" service is listed.
Run netstat -anbv and see which app runs on HTTP(S) port.
I'm using linux mint and I'm install Apache web server. When I'm testing him in web browser I can see
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet.
But if I'm trying to added one more html docs in the htdocs directory. I;m restart the server, but I have an 404 error:
Not Found
The requested URL /test.html was not found on this server.
Apache/2.2.22 (Ubuntu) Server at localhost Port 80
Now I'm open index.html which located in htdocs just after installation the server. It contains the following:
<html><body><h1>It works!</h1></body></html>
Now I'm trying to change it, but there is no effect when I'm trying to view it in browser http://localhost/index.html.
Question: What is a possible reason of this trouble?
DocumentRoot for apache2 on Linux Mint is /var/www/.
To change the default message, edit /var/www/index.html.
Put new files in /var/www/
You don't need to restart apache after updating or adding files, changes are seen immediately.