I'm trying to host my site on live server, and it gives me an error.
But when I'm running that site on localhost it runs perfectly.
My question is what is main difference in live server and localhost server.
Any one please explain me. Thanks in advance.
There is no difference but might be you have not configured the settings of your live server. In localhost it takes the normal settings automatically. Please mention your error to have better solution to your problem.
Thanks friends for your help. The problem is solved now. I made some changes in .htaccess file (rewrite rule), and it gonna works.
But I didn't get one thing that the .htaccess file on localhost is not working on live server. What is the reason, any one can explain. My server settings are same for localhost and live server.
Related
I deployed an application (usual Apache-tomcat bridge) and I am getting this message:
But cookies are enabled! I read this post but it is none of those causes. Anyway, I also commented out the Push and PWA directives - just in case. The issue persists.
Without SSL (Pure tomcat on port 8080) I do not get this message.
Can anybody help me? Thanks.
After many attempts, I tried to redirect Apache2 to the root and use the full path of the application and Vaadin stopped complaining. I deduced there was a path problem in the cookies and I added to my Apache2 SSL configuration:
ProxyPassReverseCookiePath /my-App-Path /
And Vaadin stopped complaining.
So I have a very weird problem, I have a website and when I'm connected through wifi everything is fine, chrome and Mozilla are loading my website.
But when I switch to LTE internet my website is working fine only on Mozilla. Chrome is throwing ERR_CONNECTION_RESET error. I tried turning off firewall and restarting the server, but it doesn't change anything. The website was made in Django.
On the other hand, when I'm connecting directly to IP, it's working (I see 404 from apache, but that's because it's configurated to work with domain).
I'm using also certbot, but it's not looking like certbot fault. It's rather something connected with domain configuration.
I'm using OVH services both for server and domain. In domain I added only ip4 and ip6, DNS servers were left in the default configuration.
Ok, so to fix it I removed IPv6 redirect from the domain. And now it's working. I hope that it will help someone :)
I've been trying to figure this out for a while now and nothing I've found has really been helping.
I've got a remote Linux server running with Apache installed, and right now everything going to the server is redirected to HTTPS through Apache. This all works fine and I can access the files I need to normally, but now I'd like to also add in a Django site to my server under a new "subdomain". (For example I'd like to still be able to access non-Django files as usual 'https://www.thesite.com/path/to/file.php' and also be able to access the Django site like 'https://www.thesite.com/djangosite/some/site/page')
Could someone please give me some direction as to how I'd be able to do this? I can supply more information if it's needed.
Thanks in advance!
Edit 1: The Django server seems to dislike connecting via HTTPS and I'm getting an error that it can only support HTTP, but I need it because I want the site to be secure, and currently Apache is redirecting all HTTP requests to HTTPS, so do I need some other method of making it work?
https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm
Check out SNI and also potentially wild card certificates
I am building a Facebook app using Django. So, for development, I connected the app to localhost. My app is loading on canvas and working fine but the Facebook debugger is unable to test it correctly when I give localhost address as input.
These are the requests I tried in debugger
http://localhost
https://localhost/
http://127.0.0.1/
localhost
etc
Almost for all possible combinations.. It showed me
Error Parsing URL: Error parsing input URL, no data was scraped.
When I deployed the same code on heroku and tried.. It was working!
So,
Can't I debug the project on localhost? What's the point in working on it then??
If I can work, how should I fix it?
Can't I debug the project on localhost? What's the point in working on it then??
You can debug your code etc. on localhost – but of course you can’t have Facebook’s debug tool reach a site on your localhost, because Facebook (and everyone else on the web) does have no idea what machine your localhost actually is. (Absolute bascis, dude!)
If I can work, how should I fix it?
You have to make your web server accessible from the “outside”, over the internet.
Set up your test server so that it accepts requests from outside IPs, and get a DynDNS address (basically something that can be resolved by third parties like Facebook over the DNS).
You can access Facebook apps locally but you need to fake the domain of your local computer. You can do this by adding
127.0.0.1 mysite.test.example.com
to /etc/hosts. You should update mysite.test.example.com to your domain. Your Facebook app needs to be configured for that domain. You can then use the Facebook app locally and debug your project.
The alternative is to setup up a web server and use its domain for testing purposes (but this is not ideal because you'll need to commit and build the code before you can see your changes).
i'm running a webapp on Jetty with Maven on my machine (Win7 pro X64) and i'm experiencing some weird problems:
when i try to open it on my browser - it's accessible via localhost but not 127.0.0.1 or my local address (192.168.0.14).
when someone else from my local network tries to access the app he can do it via my computer name but not via my local address.
NOTE:
ping works for localhost and 127.0.0.1. also, i can access 127.0.0.1 (80) with telnet.
windows firewall is off (stopped the service)
nothing defined in hosts file
cleaning DNS and ARP chache didn't help
on other computers in the network the app works fine and i can access it via their ip. we all share the same pom.xml.
error says - "link appears to be
please help me find out what the hell can be the problem
thanks...
after a looong evening of trying pretty much everything i think i found the problem - Skype!
after running jetty successfully on 8080 i consulted a friend and he told me about the skype issue. after shutting down skype, jetty runs perfectly on port 80 as well :)
after a quick search i found this - http://www.mydigitallife.info/disable-skype-from-using-opening-and-listening-on-port-80-and-443-on-local-computer/
NOTE: for some reason Jetty isn't throwing an exception like a server should in this situation
If you are getting genuine 404 errors, then you are obviously connecting to the Jetty server, but Jetty is deciding not to serve up your application on that address.
It sounds like you've enable virtual hosting on the Jetty server, so that the application is bound only to specific host names, and is therefore not being served up on numeric IP addresses.
I'm not sure how you've wound up in that situation though.