next »

[billeboy]

I hope this is the best place to ask this:

I am just learning to create my own server, and I finally have things running on a Linux (also new to me) box.

I have found I need to use another port for my server, because of possible port blocking by my ISP. I use port 8081.

CalendarScript 321 is up and running, with one problem: when I click on any view functions the port number is dropped from the url, and I get an Access Denied message from apache.

When performing admin functions, I enter the Application with: my.domain.org:8081/calendar_admin.cgi. All but one menu item functions properly; the port number is carried in the url except when I choose View Calendar from the menu. If  I plug the port number back into the url, the calendar is displayed properly.

When I enter the App with: my.domain.org:8081/calendar.cgi the calendar will display, but all links will drop the port number. Everything would function correctly if the port number was not dropped.

I am not familiar with perl code, if that's what I need to modify, but I could fumble through it with some direction.

Thanks for any help you can offer.

[DanO]

** When performing admin functions, I enter the Application with: my.domain.org:8081/calendar_admin.cgi... the port number is carried in the url except when I choose View Calendar from the menu. **

How did you originally start CalendarScript? With or without the port #?

I assume it was without in which case the wrong calendar_admin_url= variable value is now defined in the CalendarScript config.txt file. That file may need to be manually edited to correct that value.

** When I enter the App with: my.domain.org:8081/calendar.cgi the calendar will display, but all links will drop the port number. **

Same here although that file may need to be manually edited to also correct the value of the calendar_url= variable.

CalendarScript automatically records those values depending on what they were when the script was originally started. It may be possible that even if started with the port number in place, the server variables for those values may not have included the port number and thus incorrect values were recorded.

Dan O.

------------------

[billeboy]

Thanks for the quick easy fix.

You are absolutely right! I started out using the default server config with the calendar running in localhost. It was later that I discovered my port problem.