I've never used Parallels' Plesk before and I'm trying to get my site up and running. I was using MAMP as a local server and everything worked fine, but now getting in on Plesk doesn't seem to be working.
I've connected a domain name (toptasty.gr) to the server, I've set "toptasty.gr/" as the document root (it doesn't seem to allow a default root), and inside that directory I have all my files, including an index.php.
But when I try to see my site, Chrome tells me the DNS can't find the site. I'm out of ideas, what am I doing wrong?
Thanks
Plesk creates a root called /httpdocs where you need to place your web files. With regards to DNS issue I would say that you have setup DNS in Plesk only. You will need to add or edit your DNS details to your hosting providers DNS or if your Domain registrar allows DNS you will need to add detail there. i.e www points to your Plesk server IP. N.B. Even though you have DNS in Plesk it is not controlling your domains DNS.
Related
We are currently working on transferring websites to our own plesk environment from third party hostings. we start with the website first and then the rest. Now we have the problem that domain names whose dns points to the same plesk server can no longer mail them to each other. We have already disabled the DNS on the plesk server because it is provided externally, but it doesn't matter.
If we have the website running on the same server and want to email each other, the following error message appears:
server error 5.1.1. User unknown in virtual mailbox table
Does anyone have experience with this?
I have set up a new SSRS 2019 site with HTTPS & DNS. When I am connecting to the site through the https://ComputerFQDN/Reports then everything works just fine. When I try to connect through DNS to https://DNSName/Reports then the main page comes up and everything functions, until I try to run a report and then I get a 404 error. I can't figure out what setting I am missing or why all the reports work with the FQDN but fail with DNS alias.
Certificate is good and has the FQDN + DNS entries.
Tried with multiple DNS entries and get the same error.
Tried multiple browsers with same results and multiple computers.
I have checked that the DNS entries are both in the URL ACL and the RSReportServer.config files.
Server is configured to only use HTTPS.
Server is not running IIS.
This is an on-prem install and not in the cloud.
SQL 2019 with an Always On High Availability cluster.
I've read everything I can find, but so far I have not been able to find an answer to this problem.
Problem resolved. The DNS entries were not properly input into the URLACL for ReportServer.
When looking at the "netsh http show urlacl" command we noticed that the /Reports entries were present for the DNS entries, but were not present for the /ReportServer entry. Once we added the entries for the /ReportServer then it started working correctly.
we are using solr version 6.5.1 ,we are set the solr in server need to access the url outside server ,we using server windows server 2012 now local host weare using this url how to access this url in outside
http://localhost:8983/solr/kmartdev/select?&indent=on&defType=dismax&q=amul&qf=name+model&wt=json
When using in same network
When client is in same network, then you don't need to have a public IP of the server to access it. Follow these steps:
Find the IP of the server
Add into host file of the client, say XX.XX.XX.XX solr.com
Open http://solr.com:8983/solr/ for admin panel.
Step 2 is not mandatory, but if you dont add in host, then use IP address in browser. It will be `http://XX.XX.XX.XX:8983/solr/
When using in different network
To access the server that is not in your domain, you need to have a public IP. If you have taken the domain name then use http://yourdomain.com:8983/solr/, but if not, then add in host, or directly use IP address (steps are same as in the previous ones)
I got the answer, actually we need to open a port into our server. So, I've opened a post from control panel-> windows firewall-> inbound rules. And I've opened same port into azure server also. Now I can access my solr from anywhere.
Hope this answer will help someone and save their time. :)
Active Directory Federation Service has been installed on Windows Server 2012 along with Active Directory.
When I try to execute https:/{server-name}/federationmetadata/2007-06/federationmetadata.xml or https:/{server-name}/adfs/ls/idpinitiatedsignon.htm my internet explorer shows me host not resolvable.
I can ping the DNS server and the service seems to be running fine. No Certification errors exist. I can see entry of /adfs/ls in ADFS console endpoint tab.
What could be the reason for getting a host not resolvable error? And how can I go about fixing this issue?
I resolved the issue. I needed to disable proxy in the network options.
I am looking for a solution to my Active Directory problem.
Environment:
Attempting to authenticate users on an external Centos 6.4 website (outside our firewall) by connecting to Microsoft Active Directory which is located behind the firewall.
Currently, we use active directory within our firewall via the domain activedirectory.website.local and works fine. We are in the process of moving some of our sites to an externally hosted server so we need SSL. We have generated a self-signed ssl cert on the active directory server and have exported the ca.pem to the Centos server.
When I try to authenticate Active Directory through the terminal in the client Centos machine (located outside our firewall), I get an error:
TLS: hostname (firewall.website.com) does not match common name in
certificate (activedirectory.website.local)
This error occurs because:
I am trying to access active directory which is behind our firewall from a client computer from outside
the certificate says "Hey I'm generated from
activedirectory.website.local but you are asking for
firewall.website.com".
We talked to an SSL company about getting a commercial SSL for the .local server and they said they could sell us one for a year. Beyond that year they would not be able to extend the SSL due to some sort of regulation.
Due to the complexity of the network, I cannot change the domain name of activedirectory.website.local or firewall.website.com.
I'm sure someone has ran into this problem but I currently can't find any solutions on the web.
All I need from active directory is usernames and passwords for login authentication.
Thank you in advance!
First thing, (shitty ... caca boudin in french) can't you declare activedirectory.website.local with the right IP adress in /etc/hosts.
Another thing I see is to buy a certificate (or to create your own using your own CA) and install it on the Active-Directory service. Have a look to How to enable LDAP over SSL with a third-party certification authority.