A user may be required to update their Access URL for a variety of reasons. The most common seems to be if the Access URL is not copy/pasted properly into the form field.
If this is the case and you are no longer able to access your inBOX25 account or even the inBOX25 Setup Wizard, then you'll need to clear the Access URL entirely.
To clear the Access URL and start fresh, do the following:
1. Click on 'Update Access URL'
2. The form field will appear for your entry, leave it blank and click 'Save'
3. This will restart the setup process and you'll need to re-enter your inBOX25 credentials.
Remember, your Access URL is unique and belongs only to a single user. Although it is encoded for security, it should still not be shared or distributed.
Safari Users: Module setup
I'm using Safari on my Mac or PC and every time I paste my secure access URL into the module and click save, I'm forwarded back to the beginning of the module setup wizard.
This issue seems to occur with older versions of Safari, when there was a security option to accept cookies 'Only from sites I visit'. When this option is enabled, then Safari will ignore certain parameters that are attached to your secure access URL. The reason the browser ignores the parameters is because you're not directly visiting the inBOX25 secure access URL in your browser, its being loaded remotely in the module. And when those parameters are ignored, our security provisions are disabled and we cannot authenticate your module or account and thus your access is not granted.
The only reliable solution is to disable blocking cookies all together, run the module setup and then enable blocking cookies except for sites you visit. If you enable the blocking after your setup is successfully completed, then you will have successfully retained the session/cookie required for authentication and Safari will operate under the impression that you've already visited the site. Thus, the blocking of the module will stop but your regular browser security will still be in full effect.
As an alternative, you can switch to Mozilla Firefox as your access browser. This issue does not exist and you do not have to disable cookie blocking.
Our team troubleshot this issue using Safari 5.0.6 on a Powermac G5 and also tested in on an Intel-based Mac running Safari 6.0.