My https is working well however when i went to try run a html validator on my homepage i get an error
https://validator.w3.org/check?uri=www.lynchnetworks.ie&charset=%28detect+automatically%29&doctype=Inline&group=0
is this hosting or .htaccess or somthing does anyone know?
i have no idea where to start
Related
I'm having a problem with the backend when I deploy my site to the IIS of my web host, it has no styling. At first I had this problem with my entire site but then I added the IIS configuration code from the documentation to my web.config file in the root map and it fixed the front-end but the backend is still broken. I can still login but there is just no styling, it's a bit difficult to navigate the backend that way ;)
Here is some more info:
PHP version 7.0.19
October system build 419
IIS webserver
This is how my backend login screen look right now
I added some other code snippets that I found on the internet to my web.config file but that didn't solve the problem. Has anyone encountered the same problem? If so, could you tell me what might fix this?
Edit: Chrome Network Tab
To deploying your octobercms to server, you need to change the url parameter in config/app.php file. It's should look like this:
'url' => 'http://yourdomain.com/',
Don't forget it should contain http:// or https:// string.
Hope it helps
I've got a Laravel app that's hosted on Heroku, currently in staging environment that's password protected. It's accessible via https:// but axios is making requests to http:// and causing a cors error... I've tried adding allow origin headers as middleware on the routes but that doesn't fix the error.
Is there a way to force axios to use https by default? I don't want to pass the full URL to the axios.get()
This doesn't happen on local so could it be something caused by Heroku?
There is a Pull Request on the way that will try to access http/s if the other protocol fails. So it's a matter of time now.
I think the issue is actually related to Heroku but I can't be certain.
The only thing that tells me this is that I moved to an EC2 instance via Laravel Forge and I don't have any problems.
Strangely I also had a couple of files that were being requested without www. And when viewing in browser it forced the css files to the naked domain. What's weird though is other css files loaded with www. And weren't redirected so I think it could also have been a permissions thing.
I solved the file issue by simply changing the file name and the redirect stopped so maybe an overzealous redirect. Either way it was annoying and I think I tried everything so hopefully that information helps somebody else in future.
Cheers
I am working on Magento Soap API version 2. but During login call I am getting site complete index page HTML instead of valid data.
After Debug using Soap UI I have found that soap:address location URL is incorrect.
URL Coming: http://SITENAME/index.php/?type=v2_soap
Correct URL: http://SITENAME/api/v2_soap/?wsdl=1
I have checked in wsdl xml as well. It have default values there.
Anyone face the same issue ? Please Help !!
If you didn't change anything in Magento's code you should use this URL:
https://yourmagentosite.com/index.php/api/v2_soap/index/
if it will not work, try to use: https://yourmagentosite.com/index.php/api/v2_soap/
Also, keep in mind that some url may not work due to incorrect web server configuration, in this way you should look into web server config.
Alright,
So my main site, yorkdigitalsolutions.com is using codeigniter, on nginx and everything works perfectly, I got the redirect and all working perfect.
So I do the same for a codeigniter project I am working on, and I put it to my test subdomain etienne.yorkdigitalsolutions.com, and create the A zone like I should in Linode's dns manager and when I have just a flat html file, it all resolves and works nice, otherwise with the codeigniter project, I get error 500.
Where should I start looking for the problem?
Thanks
Alright,
So it turns out that if you need something (like a database) and codeigniter does not have access to it, it will throw out error 500.
Hopefully this helps someone in the future
I have a website built on Joomla.Everything seemed to be going fine when all of a sudden I am noticing the following.
When I go to the administrator login page, once I fill my details and press login, I am getting a 401.shtml page with following message -
"Not Found
The requested URL /401.shtml was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_perl/2.0.5 Perl/v5.8.8 Server at www.shillingstudios.com Port 80"
Now as per my understanding the 401 error would mean that I do not have the authorization to visit that page or do what I am trying to do.Maybe I am not entering the correct username or password.
However,my username and password are correct.Moreover if I go back to the admin login page I find that I am logged into the administrator panel, which means that my login attempt was successful even though I was directed to 401.shtml page.
The same thing happens when I try to logout(on refresh I find that I had successfully logged out)
When I try to Save/Edit/Close an Article/Category/Section I am redirected to the same page.But in each instance I am actually able to successfully do what I was trying to do.
The only change that I made prior to this issue was installing following plug-ins:
Set Generator tag plug-in
Title Manager plug-in
I installed both plug-ins for SEO purpose from http://extensions.joomla.org/extensions/site-management/seo-a-metadata
I thought that the issue might have caused due to installing these plug-ins so I disabled them, but the problem is still there.
I am trying to setup a website for an Android game that I am developing and Joomla seemed a good option for creating my own website. However I do not have much idea about PHP or MySQL or how Apache server works.So I am not able to determine why this is happening and what can possibly fix this, so any help will be appreciated.
You could try making sure that your website URL is in the 'live site' field in the config.php file. That can sometimes help.
First you should create your custom error pages – you can use a text/HTML editor of your choice (for example Dreamweaver). Once you are ready with the pages, upload them into a subdirectory of your public_html called errors. Then open your main .htaccess file and add the following lines in it:
serve custom error pages
ErrorDocument 400 /errors/400.html
ErrorDocument 401 /errors/401.html
ErrorDocument 403 /errors/403.html
ErrorDocument 404 /errors/404.html
ErrorDocument 500 /errors/500.html
Important settings:
Search Engine Friendly URLs: Yes
Use Apache mod_rewrite: Yes
Mod_login settings: All defaults from installation
edit:
I did rename htaccess.txt into .htaccess