I am hosting a modx website on ixwebhosting.com
After I submitted the site, I get this message when I try and access the root for example:
wwww.website.com/
or
www.website.com/manager/
I can get it to work, however, if I go directly to :
www.website.com/index.php
or
www.website.com/manager/index.php
ixwebhosting.com offers windows hosting
What do you think is causing this?
Right click on the virtual directory (gear icon) in IIS snapin, click Properties.
Check the box that says 'Directory browsing'
Click okay (and possibly?) restart IIS.
sounds like the default document setting is not "turned on" for the IIS
Related
After installing XAMPP to Windows 10 (all default/recommended installation attributes), I now have an issue changing its configuration after opening it.
Error: Cannot create file "C:\xampp\xampp-control.ini".
Access is denied
Clicking Save to a change in Configuration of Control Panel:
This "Configuration of Control Panel" box opens after clicking the "Config" button at the top right of the running XAMPP app:
I've tried a suggestion to run the XAMPP app with Administrator (elevated) access… but that seems like a major security issue, considering I don't know exactly what XAMPP would or could do with my files that require that permission, whether intended by the people who run XAMPP or not.
I've tried re-installing to another folder, like to C:\Users\Me, or a sub-folder like Documents or a custom one, but I just got different permissions issues that I struggled to figure out.
If you know a solution that worked for you, that avoided running XAMPP with Admin privileges, please let me know. I've gone through a handful of seemingly-related questions here but they seem to be related to MySQL/PHP questions and not Windows file system permissions.
I found a solution after noticing that the file already existed from apparently a past workaround I tried with running XAMPP as Admin... based on the permissions of the file being different than its parent folder. I discovered this by right-clicking the xampp folder or the xampp-control.ini file then selecting Properties and clicking the Security tab, then clicking into each attached user account's permissions.
So, my C:\xampp folder has these permissions: for Admin, basically full access; for my user account, Read, Execute, and Write.
The xampp-control.ini file has only Admin permissions; my user account is not attached to it.
Adding my user account to the xampp-control.ini file's Security, and adding Write permission then allowed XAMPP's config panel to save my changes.
Note that I typed my username into the "Enter the object names to select" box, then clicked Check Names; this auto-populated my username reference (?), though I'm not sure how it would work if it finds multiple results. Then I could click OK to get back to the Permissions box to add "Modify" and "Write" for it. I'm completely OK giving my user account permission to modify and write to this file through the XAMPP app.
Now, that fixes that file for that scenario; now I'm wondering if there will be other permissions issues with other files, because I noticed some other files (that I checked randomly) don't all share the same permissions for my user account!
Maybe I should have instead modified the xampp folder's permissions recursively to give my user account Write and/or Modify access (I'm not sure of the difference, Windows permissions seem far more complicated to understand and use than Linux's and Mac's do).
I think the file permissions were all set by XAMPP during install; I don't know yet that expanding permissions on certain files will not create new problems...
I found a solution after noticing that error, here is my solution
go to xampp installation folder on the c drive
Xampp Destination
then find xammp control panel.exe
Xampp Control Panel
then right click and go to properties(or press ALT+ENTER)
Click Properties
then go to compatibility and enable Run this program as an administrator
Compatibility tab
Your Problem is now fixed
We just virtualized a Windows server in Azure and everything in working fine on Client side, but we are not being able to solve the indexing search problem.
When you have a local drive, Windows can index the path and searches works fine using Windows menu/search box in task bar. But for shared drives it seems to fail.
In Windows Explorer the search pretends to work, but it takes forever to find a file or folder. And sometimes it just won't move anywhere. So it is not an option for users since them are used to search using menu bar.
We have tried to change drive properties in Right button to Shared Driver > "Allow files on this drive to have contents indexed in addition to file properties, but it was already enabled.
When we try to disable it, it prompts an error saying that the user doesn't have permission to do it, but it does anyway. And when we try to re-enable, the message prompts again, but it is enabled with no problem at all. But once again, nothing changes and Initial Menu Search just won't work.
Does anyone knows if there is a solution for that?
For me it seems to be an server setup since I see that permission error, but, as far as I know, if the shared driver is already mounted, I can't see a reason why Windows can't index it.
Ps.1: In the shared drive security tab, the System has full permissions.
Ps.2: If there is a solution for this, is that possible to solve it on the Windows server Side so we won't need to access client by client to change it manually?
enter image description here
Please check the following setting and see.
1.First thing is to check network location is being indexed. open File Explorer right-click on the mapped network drive that you need to index, then select the Properties and Make sure that, the Allow Files on this Drive to Have Contents Indexed checkbox is selected.
You have already done this step
2.try to check the search options for network drive in file explorer, go to view tab>>click on Options Icon and choose the change folder and search option menu it will open the folder options dialog box and select search tab and make sure first option is not selected
3.check server side Indexing
4.we need to make sure search service needs to be running.
Open services.msc check for the wndows search service and try to restart the service.
5.Go to Settings on the Windows 10 desktop, then click on Search, followed by Searching Windows scroll down and try to run the indexer troubleshooter
Reference https://learn.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/fix-problems-in-windows-search
I am using MacBook Air. I installed the xampp but it's not working.
After some research, I found the URL http://localhost:8080/dashboard/ and I am getting the xampp. Now I am confused where should I get htdocs folder to add my code. Can anyone assist me?
Let's talk about in details
I downloaded the xampp from this link https://www.apachefriends.org/download.html
and I move it on the application. Now I am getting the xampp icon in application.
Then I open the xampp and I got a popup like and I click on start
I enable the 8080 port number.
Then I just I checked in the browser http://localhost:8080/dashboard/ and I found the xampp dashboard page.
Now I am not getting the htdocs folder. would you help me out in this?
I too have had lots of confusion setting up XAMPP on my Mac.
Things the docs said would work, just plain did not.
The short answer to your question: In MacOS X the htdocs dir of the virtual server is in:
/Users/<YOUR-USER-NAME>/.bitnami/stackman/machines/xampp/volumes/root/htdocs
More complete instructions for getting the server up:
Open up the XAMPP Application
Under General/Services start the XAMPP services
Under Network make sure to enable a port config (I chose localhost:8080->80)
In the Volumes "tab" click "Mount" beside /opt/lampp and then you can click "Explore" to open a finder window to the virtual server.
This will cause the virtual Network-Drive 192.168.xxx.yyy to show up in the Finder sidebar which has a single folder named lampp
Additionally a new external drive named lampp will also be available in Finder.
However you get to lampp, put your source-files in the htdocs folder.
Links that DID work for me on first launching:
http://localhost:8080/dashboard/
http://localhost:8080/phpmyadmin/
http://192.168.64.2/dashboard/
Links that did NOT work, in spite of docs claiming otherwise:
http://localhost/ or http://localhost/index.php
http://192.168.64.2/phpmyadmin/ <--Access Forbidden 403
A little late to the thread but I hit and solved this issue and I believe the OP had downloaded and installed the wrong version. At the time I am writing this, the link on the downloads page is for .dmg file is a VM file, or at least missing features of the full download. Instead of downloading that, go to the more downloads section
Once there, choose the version you need for your OS. This, and some mysql tweaks that are answered in multiple connected topics got me running.
Your XAMPP is working fine. You have to use Finder to go to htdocs.
Follow these steps -
Open the XAMPP application and hit "Start" button.
Make sure everything is proper by hitting "Go to Application".
Now you should see the dashboard on your browser, if not, restart the application and try again.
Go to Finder and on the sidebar you should see a volume labeled "192.168.64.2", go there and you will find a folder named "lamp".
See under the locations section
Inside lamp there will be htdocs, where you can place all the files you want the browser to access.Click on lamp
I have just added a new Win2012 IIS8 server to my website. The main part of the site is working fine, but I have a problem with a virtual directory. The physical path points to an IP address (\192.168...). The 'connect as' user is set correctly. 'Test Settings' reports no problems. The setup matches precisely other servers on my site (except that they are IIS 7).
The problem happens when I click 'Edit Permissions' for the virtual directory. Instead of seeing properties for the directory, I see properties for 'System32'. I cannot set permissions for the virtual directory, and so I can't serve files from it.
On another server, 'Edit Permissions' behaves properly. I can see the permissions assigned to users on the Linux box. If I 'Add' to add another user, the 'Location' box shows me the Linux server IP, and I can add a Linux account.
I can browse, view, and edit files though Windows Explorer on the Linux server, so there is no connectivity problem. But IIS doesn't see it.
I feel like I missed a step somewhere - any ideas out there?
Found the answer over on serverfault (which is probably where I should have posted in the first place...). The allowSubDirConfig value for the site needed to be set to 'false'.
Details here
I am having this issue on my Win XP Professional Development Machine. My application is on Virtual Directory.
The current identity (MachineName\ASPNET) does not have write access to 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
I have done following so far.
1. Must Not Use Simple File Sharing. After Changing Settings, Pls Reboot.
Open your My Computer, the on menu, select Tool >> Folder Option the Select View Tab,
Uncheck Use Simple File Sharing
2 Adding User Permission
When you create virtual directory on IIS, the actual folder you used with it must have access permission
To do this, follow:
select the properties of your actual folder, then select Sharing Tab
select option Share This Folder
specify the ShareName (commonly folder name itself)
then select Security tab, you will see the Group and Username listed there.
to add ASPNET just click ADD
pop up window will appear "Select User or Group"
Click Advance and Click Find Now
All Users and Group will be listed there, try to find ASPNET and select OK
you will going to back on Security tab and select something like "RAD/ASPNET", under that you will see "Permission for ASP.NET"
for the last step, check Full Control under Allow Column, then OK
3 I Have tried, the aspnet_regiis exe in the framework folder!
Still does not work, Any other options or suggestions please..
Update:
My Hard disk is completely encrypted. Does it have any impact?
Encrypted shouldn't affect.
Try going to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files in a file windows explorer and give all access to your ASPNET and Network accounts.