Wiki Server 2: "Access Forbidden!"

Hi all,
Suddenly today (after a reboot) our wiki pages started responding with the Error 403 "Access Forbidden" page... As seen here: http://www.celadonsound.com/groups
I can't seem to figure out why this has happened. I'm sure I could do with supplying a lot more information but I guess I'm going to need you guys (and gals) to shout at me before I realise what information I should be including...
Up until today the wiki pages performed perfectly now I get that 403 error when trying to access them on the web..
Also my calendars have stopped syncing displaying:
"The server responded with
“HTTP/1.1 500 Internal Server Error”
to operation CalDAVAccountRefreshQueueableOperation."
Both the calendars and wikis worked just fine yesterday and nothing has been changed on the server aside from a reboot because I had to move the unit.
I have tried many things, including ensuring that the Collaborations folder and its contents have the correct _teamsserver r&w permisions. Which they do.
Below is the error log for the wiki server since a couple of service restarts ago:
2011-07-20 18:35:17+0100 [-] Log opened.
2011-07-20 18:35:17+0100 [-] twistd 8.2.0 (/usr/bin/python 2.6.1) starting up.
2011-07-20 18:35:17+0100 [-] reactor class: twisted.internet.selectreactor.SelectReactor.
2011-07-20 18:35:17+0100 [-] Current log level is warn
2011-07-20 18:35:17+0100 [-] twisted.web.server.Site starting on 8086
2011-07-20 18:35:17+0100 [-] twisted.web2.channel.http.HTTPFactory starting on 8087
2011-07-20 18:35:17+0100 [-] Starting
2011-07-20 18:35:18+0100 [-] in migration. repo version is: 23
2011-07-20 18:35:18+0100 [-] Running
2011-07-20 18:49:25+0100 [-] Received SIGTERM, shutting down.
2011-07-20 18:49:25+0100 [-] Stopping
2011-07-20 18:49:25+0100 [-] userPrefsFlushLooper stopped looping, doing final flush
2011-07-20 18:49:25+0100 [-] mailingListFlushLooper stopped looping, doing final flush
2011-07-20 18:49:25+0100 [-] Main loop terminated.
2011-07-20 18:49:25+0100 [-] Server Shut Down.
2011-07-20 18:49:28+0100 [-] Log opened.
2011-07-20 18:49:28+0100 [-] twistd 8.2.0 (/usr/bin/python 2.6.1) starting up.
2011-07-20 18:49:28+0100 [-] reactor class: twisted.internet.selectreactor.SelectReactor.
2011-07-20 18:49:28+0100 [-] Current log level is warn
2011-07-20 18:49:28+0100 [-] twisted.web.server.Site starting on 8086
2011-07-20 18:49:28+0100 [-] twisted.web2.channel.http.HTTPFactory starting on 8087
2011-07-20 18:49:28+0100 [-] Starting
2011-07-20 18:49:28+0100 [-] in migration. repo version is: 23
2011-07-20 18:49:28+0100 [-] Running
Hopefully someone will be able to help as this is terrorizing me at the moment
Many Thanks,
Elliott

We have the same need: Opening a Link in an wiki article in a blank window - how to?

Similar Messages

Can't Host a Wiki Server's calendar using Server 10.8

I have setup server and attempted to have one of my calendars on iCal sync with the Wiki calendar
I have a user called bernard
I have a calendar in ical called bernardtraining
In the Wiki the user bernard has a calendar but I cant get ical to sync with the Wiki.
In iCal Accounts
I set up an account in ical lets call it server.myserver.private (hiding actual name)
user name = bernard
password is set to user password
Refresh 5 minutes
In Server Settings iCal Accounts
Server address server.myserver.private
server path aut populates to /principals/__uids__/7A7D303D-8265-47D5-BAD1-01E3DDD4CC37/ (maybe this is the problem)
Port = auto
SSL = No (for now)
No delgates
I then went through this process.....
When you set up iCal Server to provide the calendar service for a wiki, Wiki Server provides access to the calendars, so users who do not have wiki privileges do not have calendar service.
Use serveradmin via the Terminal app to change the setting.sudo serveradmin set calendar:Authentication:Wiki:Enabled = "<setting>" The default value for <setting> is “no”.
The other possible value is “yes.”
Command example:
sudo serveradmin set calendar:Authentication:Wiki:Enabled = "yes"
Use serveradmin via the Terminal app to designate the Wiki server.sudo serveradmin set calendar:Authentication:Wiki:Hostname = "<DNSWikiServer>" The default value for <DNSWikiServer> is the Wiki server’s fully qualified domain name.
Command example:
sudo serveradmin set calendar:Authentication:Wiki:Hostname = "wikiweb.example.com"
Use serveradmin via the Terminal app to encrypt the connection.sudo serveradmin set set calendar:Authentication:Wiki:UseSSL = "(yes|no)" The default value is “no”.
Command example:
sudo serveradmin set set calendar:Authentication:Wiki:UseSSL = "yes"
Still no success.
Can anyone help?

I did, and had it working last night. It won't now, though.
I don't understand port triggering, and when I attempted to look up the help files on the linksys site, they told me to register first - then they wouldn't let me fill in the email address section of the registration, so..
I don't use a firewall, and this computer I'm trying to host the server on is directly connected to the router. The wireless connection is with a laptop upstairs. I just checked, and my IP changed, but fixing that in Port Forwarding still does nothing. I can host the server... It just doesn't show up on gamespy.
Just about everywhere I read up on this, it mentions having to have a static IP address. I went through the guides that tell how to go about getting one set up, but still doesn't work. I don't have anything even remotely mentioning linksys in Network Connections though - that's on the laptop. Could this be the problem?
Another problem I ran into when setting up the router, was I'd get an error unpacking languages, or something. Got it every time, but it let me move on after closing the error so didn't think much of it.

Server Error 403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied.

Hi,
I`d like to get your advice on Server Error 403 - Forbidden: Access is denied. I use to visit a webpage with no issues so far but now i getting this error each time i`m trying to get into. Any ideas in how to solve it? A step to step process will be highly appreciated.
Thanks.
PS, I`m using the latest safari 8.0.3 and OS X 10.10.2.

It's an error message from the web server, not from Safari. There's a slight chance that you might be able to clear it as follows.
From the Safari menu bar, select
Safari ▹ Preferences... ▹ Privacy ▹ Remove All Website Data...
and confirm. Test.

Mobile Access + Wiki Server via SSL Question

If MAS is running with SSL, does that SSL continue for the entire session? Or just the initial passing of credentials?
I'd like to not have the wiki server running SSL for internal use if MAS encrypts all the traffic. The reason for the question is when connecting to the wiki server via MAS, there is no SSL lock on the browser, telling me it's in the clear.

Mobile Access Server does not provide proxy access to 10.6 server Wiki.
hth,
b.

Leopard Server - Web User folder - Access forbidden

Hi,
we migrated our users from a Tiger server to a Leopard yesterday. Now all of them have 'access forbidden' errors on their web.server.com/~username folders.
There are read-only permissions on their sites folder and we can access the default server home page.
I have seen the posts for deskop 10.5.4 stuff for personal web sharing but that doesn't apply here.
Any ideas?

I should say that the _www user/group is a system user/group, and therefore its hidden from the typical list of users and groups. I don't have a Leopard server in front of me, but there is a way to view system users and groups in the list. Hopefully your engineer knows it off the top of his head.

Wiki Server Closed on iPad

I start Wiki Server as normal. However iPad has no access to the Wiki Server. It says "Wiki Server Closed".
But other devices (Windows/Mac/Linux/iPhone) works quite good.
This is the information I got in ngrok. Maybe this will help find a solution.
GET /wiki/ipad/ 403 Forbidden
I would appreciate if anyone could help me.

solved by adding /wiki/ /wiki/ipad/ to the index

WL 5.1 and IIS - HTTP Error 403 - Access Forbidden problems

I'm trying to hook IIS up to the evaluation version of WebLogic Server 5.1
that I installed...
I followed the instructions that I found on the Installing the Microsoft-IIS
(proxy) plug-in page. I then copied HelloWorld.jsp into the
d:\weblogic\myserver\public_html directory, and tried to bring it up in a
browser by typing in localhost/HelloWorld.jsp. At this point, I got the
following error:
** Begin error message **
HTTP Error 403
403.1 Forbidden: Execute Access Forbidden
This error can be caused if you try to execute a CGI, ISAPI, or other
executable program from a directory that does not allow programs to be
executed.
Please contact the Web server's administrator if the problem persists.
** End error message **
I then tried adding a virtual directory called public_html to my default Web
site. This didn't help. I even tried creating a directory called public_html
inside public_html, setting execute privilages on it, and putting a copy of
HelloWorld.jsp in there. This allowed me to type
localhost/public_html/HelloWorld.jsp into my browser, and to see the JSP
source code!?#...
This is what my iisproxy.ini file looks like (It lives in d:\weblogic):
** Begin iisproxy.ini **
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicHost=localhost
WebLogicPort=7001
WebLogicCluster=
ConnectTimeoutSecs=20
ConnectRetrySecs=2
** End iisproxy.ini **
Any suggestions/help from someone who's done this before would be greatly
appreciated. We can't run/evaluate the product before we can crawl and walk.
Cheers...
Dave Bruzzone
WebCredenza, Inc.

Thr problem is that you must set Execute rights to the IIS web at the
Configuration settings (exactly as seen in the documentation).
"Davide Bruzzone" <[email protected]> ha scritto nel messaggio
news:8iubob$mgp$[email protected]..
I'm trying to hook IIS up to the evaluation version of WebLogic Server 5.1
that I installed...
I followed the instructions that I found on the Installing theMicrosoft-IIS
(proxy) plug-in page. I then copied HelloWorld.jsp into the
d:\weblogic\myserver\public_html directory, and tried to bring it up in a
browser by typing in localhost/HelloWorld.jsp. At this point, I got the
following error:
** Begin error message **
HTTP Error 403
403.1 Forbidden: Execute Access Forbidden
This error can be caused if you try to execute a CGI, ISAPI, or other
executable program from a directory that does not allow programs to be
executed.
Please contact the Web server's administrator if the problem persists.
** End error message **
I then tried adding a virtual directory called public_html to my defaultWeb
site. This didn't help. I even tried creating a directory calledpublic_html
inside public_html, setting execute privilages on it, and putting a copyof
HelloWorld.jsp in there. This allowed me to type
localhost/public_html/HelloWorld.jsp into my browser, and to see the JSP
source code!?#...
This is what my iisproxy.ini file looks like (It lives in d:\weblogic):
** Begin iisproxy.ini **
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicHost=localhost
WebLogicPort=7001
WebLogicCluster=
ConnectTimeoutSecs=20
ConnectRetrySecs=2
** End iisproxy.ini **
Any suggestions/help from someone who's done this before would be greatly
appreciated. We can't run/evaluate the product before we can crawl andwalk.
>
Cheers...
Dave Bruzzone
WebCredenza, Inc.
[isapi2.gif]

[SOLVED] Apache Access forbidden Error 403 localhost

Hello,
I believe this should be some thing very stupid, but I can't find it... so here I am.
I have just installed apache (# pacman -S apache)
Configured httpd.comf, and created 2 virtual hosts with extra/httpd-vhosts.conf
When I believed every thing was ok, I have started Apache as root (# apachectl start)
Started ok, no errors (also tried start it as user with sudo, and /etc/init.d/httpd start)
So when I go to http://localhos (or the virtual host) I allways get Access forbidden Error 403
I have set 777 permissions to /srv/http and the virtual host (/home/username/local-web/site1.dev)
I have tried every thing , changed dir owners to "http:http" ...
At the Apache error log I get:
"[Thu Oct 29 02:39:48 2009] [error] [client 127.0.0.1] (13)Permission denied: access to / denied"
There is a very simple plain index.html file at /srv/http and the virtual host, all file/dir permissions very permisive... so that can't be the problem.
Am I missing some thing? Do I need to manually create the "http" user and/or add it to some group?
Last edited by iopo (2009-10-29 22:06:59)

Ok, here's the code:
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
# with ServerRoot set to "/etc/httpd" will be interpreted by the
# server as "/etc/httpd//var/log/httpd/foo_log".
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "/etc/httpd"
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
Listen 80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule substitute_module modules/mod_substitute.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule log_forensic_module modules/mod_log_forensic.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
# LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User http
Group http
</IfModule>
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/srv/http"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "/srv/http">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
# Options Indexes FollowSymLinks
Options Indexes All
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
<Directory "/home/gral/web-sit/local">
Options +Indexes FollowSymLinks +ExecCGI
AllowOverride AuthConfig FileInfo
Order allow,deny
Allow from all
</Directory>
# this was just a test
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "/var/log/httpd/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
<IfModule log_config_module>
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
CustomLog "/var/log/httpd/access_log" common
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "/var/log/httpd/access_log" combined
</IfModule>
<IfModule alias_module>
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
</IfModule>
<IfModule cgid_module>
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#Scriptsock /var/run/httpd/cgisock
</IfModule>
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
<IfModule mime_module>
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
TypesConfig conf/mime.types
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#AddType application/x-gzip .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
Include conf/extra/httpd-autoindex.conf
# Language settings
Include conf/extra/httpd-languages.conf
# User home directories
Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

Custom sidebars in Wiki server

Apple's Wiki Server and Podcast Producer are one of the best if not the best product for serving podcasts BUT this application fails in certain areas that easily puts customers off considering that companies will always vie for a Pc solution.
My major issue with the Wiki server is the custom sidebar addition. Now this should so simple to add but if you try and add a custom sidebar following apples help directives below
Adding a sidebar to the home page
The home page of your wiki automatically displays items that are tagged "hot" in a sidebar, so that users will be more apt to notice them. If you're the site owner, you can add another sidebar that spotlights items tagged with another tag of your choosing.
*To add a custom sidebar:*
*Open your site's homepage and then click the Edit (pencil) button.*
*Click the Groups Settings button.*
*Click Sidebar and enter the tag that will be used to identify items to appear in the sidebar, such as "projectX."*
*Enter a title for sidebar, such as "Project X News," then click OK.*
*Click "save" in the toolbar to save your changes.*
*The five most recent Items tagged with the tag you specified will automatically appear in the sidebar.*
First the edit pencil in the home page does not provide one the capability to edit the custom sidebar settings but the actual appearance of the page such as the text and placement of media etc.
The custom sidebar settings can only be accessed via the Admin Functions/ settings/ even then you can add a single custom side bar and when you try to add another you will find that the details of the last custom sidebar is still in place. If you delete that information and add new information this will delete the previous custom sidebar creating a new one. Now this is such an annoying issue that Apple needs to resolve ASAP as some of us are trying to sell this product for it's other benefits.
Another area that it fails at is the display of items. Currently the maximum number of items displayable is 5. To increase this requires messing about with theme files and plist files! Now this should also be a simple feature that should exist in the Admin Functions settings area. Unless I am missing something then someone should enlighten me as to the mystery of these settings. I hope Snow leopard will have all these basic issues ironed out.

by "custom fields" i mean some additional fields. e.g i want a clerk to mail a minute sheet along with remarks of clerk, to an officer. now i have put some fields e.g clerk's name, type of mail (minute sheet etc), officer's name etc on the email form (i have designed that form in java and using javamail api to send/receive mails). while sending this email, clerk fills those fields and mail it to the officer. now depending upon the type of mail (if its a minute sheet or whatever), that mail should be opened in the appropriate form designed for that type of mail, showing all those additional fields, e.g clerk's name in clerk's name label, officer's name in officer's name label etc. is it possible that i can tel exchange server to store the information about those custom fields while storing the mail so that i can retrieve those fields later. hope u got my point.thanks

Message Display Tool Access Forbidden.

Hello,
I need to review a response from a BAPI and as I understand the only place to do this is through the RWB. I went out and looked in the Adapter Engine under Message Monitoring, but when I click on the Details button and try to go to "Message Contents" I get an Access Forbidden message.
Is my SAP user ID being passed there, and if so, what role is needed to turn this back on?
Thanks!

Hi,
>I need to review a response from a BAPI and as I understand the only place to do this is through the RWB. I went out and looked in the Adapter Engine under Message
go to:
- TCODE SXBM_ADM
- integration server config
- then add those two specific parameters:
a) runtime | logging | value = 1
b) runtime | logging_sync | value = 1
fire the BAPI and go to SXMB_MONI
Regards,
michal

Wiki Server - People - suppress for unauthenticated users

With Wiki Server 4 (Server 10.8.1), unauthenticated users hitting the web server's default home page are presented with Wiki Server's default landing page listing:
"My Documents"
"All Activity"
"Wikis"
"People"
If an unauthenticated user tries any of the first three items they get no content, which is great (althouh only the "My Documnets" page prompts for credentials — I think they all should).
However, if they hit the "People" item, it lists (exposes) all of the people on your system.
We don't want a list of our users exposed — we think if you are unauthenticated, you shouldn't see anything when clicking on "People".
Suggestions?

******** PLEASE BEFORE DOING ANYTHING COPY THE CONTENT FOLDER OF THE SERVER.APP AND BACK IT UP SOMEWHERE SAFE**************
I have been working on this for weeks..... I understand some people want to be able to share there blogs and people pages but you have to understand some people don't
"People pages" should be set up is the same way as wikis... The owner(s) have the ability to give access to whom they choose. If it is a public "people page" it shows up in search and activity, if it is private it doesn't show up (or only shows up in search results with people that have access). I also feel you should have the ability to choose whether a person has a "people page" or not.
But it is what it is. So I'll step through what I did to make it work for me. You do lose some services but this was my goal....
1. All activity does not work
2. Search does not work
3. tags do not work (I hope to fix this because I want tags....)
4. iPad now brings up the PC version of the wiki server, which eliminates the ability to upload files. Some one with some java script experience maybe able to help us out but at this time I just chose to remove it....
**The other thing to note is the iPad version is completely independent of the PC version (I address this also) so even if you make all these fixes someone with an iPad will still be able to search and gain access to people unauthenticated***
Now all services (including the home page and people) need authentication to gain access.
************** Once complete you need to stop/restart wikis**************
**************I recommend making a copy of the content file of your server app (just incase)**************
Step 1. Set up authentication: (SAVE A COPY ON THE DESKTOP BEFORE EDITING)
1.Edit the controller for the wiki
/Applications/Server.app/Contents/ServerRoot/usr/share/collabd/coreclient/app/co ntrollers/application_controller.rb
2. find the block
   helper_method :service_client, :current_user, :current_version, :page_context, :use_inline_webauth, :javascript_includes_for_locale
   helper_method :webcal_enabled?, :webmail_enabled?, :entityURL, :iphone, :ipod, :ipad
   before_filter :master_before_filter, :block_older_internet_explorer
   after_filter :master_after_filter
3. Change to
   helper_method :service_client, :current_user, :current_version, :page_context, :use_inline_webauth, :javascript_includes_for_locale
   helper_method :webcal_enabled?, :webmail_enabled?, :entityURL, :iphone, :ipod, :ipad
   before_filter :master_before_filter, :block_older_internet_explorer
   before_filter :ensure_user_is_authenticated
   after_filter :master_after_filter
2. Remove search/all activity/tag access (SAVE A COPY TO DESKTOP BEFORE EDITING)
Go to:
/Applications/Server.app/Contents/ServerRoot/usr/share/collabd/coreclient/config /routes.rb
I removed the following lines of code:
    match "/updates" => redirect("/wiki/activity")
    match "/updates/:path", :to => redirect {|params| "/wiki/activity/#{params[:path]}"}
    match "/activity", :to => 'activity#index'
    match "/search", :to => 'find#index'
    match "/search/:id", :to => 'find#index'
    match "/find", :to => 'find#index'
    match "/find/:id", :to => 'find#index'
3. Remove activity from menu bars (SAVE A COPY TO DESKTOP BEFORE EDITING)
Go to:
/Applications/Server.app/Contents/ServerRoot/usr/share/collabd/coreclient/config /initializers/register_apple_plugins.rb
I removed these lines of code:
    BannerLinks::Project::Activity,
    BannerLinks::Project::Documents,
    BannerLinks::Project::Tags,
    BannerLinks::Person::Activity,
    Sources::Activity,
   Sources::MyFavorites
4. Redirect iPad to the PC version of the wiki server. (SAVE A COPY TO DESKTOP BEFORE EDITING)
Go to:
Applications/Server.app/Contents/ServerRoot/usr/share/collabd/coreclient/app/con trollers/application_controller.rb
Change:
      if ipad and ios5plus
      redirect_url = "/wiki/ipad/#route=#{request.fullpath}"
      logger.info("Redirecting to #{redirect_url} because we detected an iPad running iOS5+")
      redirect_to redirect_url
      end
To:(You could probably just remove these lines but I was still troubleshooting at the time)
      # if ipad and ios5plus
      # redirect_url = "/wiki/ipad/#route=#{request.fullpath}"
      # logger.info("Redirecting to #{redirect_url} because we detected an iPad running iOS5+")
      # redirect_to redirect_url
      # end

How to disable Wiki Server Welcome emails

I am running OS X Server 10.9.2, and I have a Wiki Server set up. Whenever I give a user access to a Wiki, the user gets an email notification. Is there anyway I can disable those notifications?
I see on previous versions there was an option:
If you want the server to send an email notification to everyone with access to the wiki, select “Send welcome email to new members.”
However, I don't see that option anywhere on this version of the Wiki Server.

Try the OS X Server forum.

Wiki server sharing permissions aren't working.

The sharing permissions or my documents in the wiki server don't seem to be working. All of my documents are set to no access for logged in and unauthenticated users. However I can still see my documents listed and accessible in the All Activity section of the wiki server when I am logged out. This is a real problem. Any ideas?

I spoke with Apple yesterday. This issue is being elevated to the appropriate team as a definite problem. The workaround for now is to set the permissions to read or read/write, click OK, then go back in and set it ot "no access" and click OK. This should set and reset the permission for the document.
It worked for me.

Wiki Server 3: What is API URL for AtomPub/MetaWeblog?

Previously (OS X Server 10.6), AtomPub/MetaWeblog editors could connect to Wiki Server using the API access point http://example.com/RPC2 (Command Line, Ecto/Marsedit)
Now (OS X Server 10.7), attempts to hit /RPC2 are resulting in a 404 response. I've so far been unable to track down where the API access point has moved to, and didn't have any luck flailing around at other likely candidates (thanks, ecto list of common XML-RPC endpoints!)
Does anyone know where Lion Server puts the XML-RPC access point?

If you want to run wikis for a couple users the Lion wiki server is easy to use and you can establish several wiki pages. We've been using Wikis on our home Mac Mini Server for a couple years and hvae several wikis to assign different permissions - one the kids can write, one the kids are just read-only... They've been quite helpful. And maintaining them if carefree - I've had NO problems. And if by maintaining you meant publishing content, that's fine too (although not completely flexible).
Having upgraded from 10.6 to 10.7 this fall, I will say that I preferred the 10.6 Snow Leopard Wiki over the new implementation, for example it offered several templates for customizing the Wiki look, editing CSS.., but those are gone now. Oh well, progress???
Regarding manuals for Lion Server I've only seen the online manauls. Snow Leopard Server had a much more comprehensive set of manuals so you may learn more about the wiki reading them than anything available for Lion (of course Lion and SL have many differences http://manuals.info.apple.com/en_US/WikiServerAdmin_v10.6.pdf
If you haven't run Mac Server before, there will probably be some learning curve pain involved, but we find it useful to run as a File Server (files, music, photos, videos), Time Machine Backup Server, WIki Server Mail Server, Mobile Home Accounts, and we'll even log directly into the server and use it as a desktop (but there are some tricks for using an account both locally and over the network). If you have some of these broader needs consider implementing Mac Server. If you just ned the wiki, implementing another wiki product may offer

Specify a distinct hostname for Wiki Server

I'd like to serve a website from www.mydomain.com and serve the wiki from wiki.mydomain.com
how do I set the wiki URL in Mac OS X Lion Server?

In the Lion Server under Web Services/Web, make sure the service is on and you have your IP address here directed to /Library/Server/Documents/Web/Data/Sites/Default
To set up the domain you have to have access to your domain webdirection with your domain name registration. Currently you have www.mydomain.com pointing at your IP address and it picks up your website (I assume). Here you also need to set up subdomains for any other services you want e.g.:
server.mydomain.com pointing to your server IP address
then you can access your web services: server.mydomain.com/wiki, server.mydomain.com/webcal
you could set up another subdomain just for the wiki:
wiki.mydomain.com pointing to the server IP address plus /wiki (e.g. 1.2.3.4/wiki)
Hope this helps

Wiki Server 2: "Access Forbidden!"

Similar Messages

Maybe you are looking for