migrating TYPO3 6.2.31 to TYPO3 7.6.23

Question

When I try to migrate my TYPO3 6.2.31 to 7.6.23 I've got some problems.

Especially the page tree is missing so I got this error

The requested resource "%2Fmain" was not found

I've tried this way to migrate:

1.) Copy the whole page

2.) Changing the symlinks to the new sources

3.) Starting the migration wizard in install tool

And now When I want to access the backend I got the above mentioned error.

what can I do?

thanks.

When I call url.de/typo3 the follwing url is called:

index.php?route=%252Fmain&token=XXX

The correct one should be

index.php?route=%2Fmain&token=XXX

What could be the problem in the url?

Try deleting caches via installtool (or hole typo3temp). Did seen the same in TYPO3 8.7, which helped in this case. Sometimes OPcode/APC can be the issue, if you change symlinks. — jokumer, Sep 21 '17 at 13:22
Yes I already have cleared all cache. In the error massage the following hint is linked: https://wiki.typo3.org/Exception/CMS/1425389240 — Felix, Sep 21 '17 at 13:58
but this does not work in my context because I cannot import anything... only the error message is shown — Felix, Sep 21 '17 at 13:59
Did you followed `Check for broken extensions` from installTool? — Ravi Sachaniya, Sep 22 '17 at 04:47
Did you found a solution. We have same issue, since switch to SSL. Only backend is broken, as soon as we are logged in. Different machines tested. Hoster self said - he can login. Same installation on other hosts running without problems. — jokumer, Sep 28 '17 at 07:53
Yes I found the Problem! Typo3 was running in a docker container and the routing was done as proxy Reverse in isp config. — Felix, Sep 28 '17 at 11:51
You have to configure the proxy correctly. I post the solution — Felix, Sep 28 '17 at 11:51

Pravin Vavadiya · Answer 1 · 2017-09-22T03:39:52.933

1

Please follow below steps.

edited Sep 22 '17 at 03:39

answered Sep 21 '17 at 15:58

Pravin Vavadiya

Thanks tried this, but I got the same error Message – Felix Sep 21 '17 at 22:29
Any hints for me? – Felix Sep 22 '17 at 08:41
you need to check log history. i think you can determine your problems on this way.. – Pravin Vavadiya Sep 22 '17 at 09:25
also don't use **Stop Page Tree** for root template – Pravin Vavadiya Sep 22 '17 at 09:32
I'm a bit closer to the problem! Backend works ... Problem added in question above – Felix Sep 22 '17 at 09:34
if use realurl then disable it and remove .htaccess file – Pravin Vavadiya Sep 22 '17 at 10:14
realurl is disabled and I have only a htaccess with a passwd hat the momet – Felix Sep 22 '17 at 12:33

score 1 · Accepted Answer · answered Sep 28 '17 at 11:53

Issue 1: Apache believes that's an invalid url

Solution: AllowEncodedSlashes On in httpd.conf

Issue 2: Apache decodes the encoded slashes

Solution: AllowEncodedSlashes NoDecode in httpd.conf (Requires Apache 2.3.12+)

Issue 3: mod_proxy attempts to re-encode (double encode) the URL changing %2F to

%252F (eg. /example/http:%252F%252Fwww.someurl.com/)

Solution: In httpd.conf use the ProxyPass keyword nocanon to pass the raw URL thru the proxy.

ProxyPass http://anotherserver:8080/example/ nocanon

httpd.conf file:

AllowEncodedSlashes NoDecode

<Location /example/>
  ProxyPass http://anotherserver:8080/example/ nocanon
</Location>

2 Answers2