[Flow] Get an 404 error after switching to "production"-context

[Mira]

Here is my vhost:
 

<VirtualHost 192.168.41.70:443>
DocumentRoot /var/www/flow3/red_dev/Web
ServerName portal.timbo.local
ErrorLog /var/www/flow3/timbo/apache-logs/error_log
CustomLog /var/www/flow3/timbo/apache-logs/access_log combined
SetEnv FLOW_CONTEXT Production
#SetEnv FLOW_CONTEXT Development
SSLEngine On
SSLCertificateFile /var/www/flow3/timbo/ssl/certs/portal.timbo.local.pem
SSLCertificateKeyFile /var/www/flow3/timbo/ssl/private/portal.timbo.local.key
</VirtualHost>

My Routes.yaml:

-
  name: 'index Startpage'
  uriPattern: ''
  defaults:
    '@package': 'My.Timbo'
    '@controller': 'Standard'
    '@action': 'index'
    '@format': 'html'

 

My Settings.yaml:

TYPO3:
  Flow:
    persistence:
      backendOptions:
        driver: 'pdo_mysql'
        dbname: 'red_portal'
        user: 'red_portal'
        password: 'redp0r!ald4t4bas'
        host: 'ilss-db01.ilss.local'
#     il8n:
#     defaultLocale: en

 

 

 

 
 
 

> Carsten Bleicker <carsten at bleicker.de> hat am 3. März 2015 um 13:58
> geschrieben:
>
>
> Maybe you can put some of your configs to gist including the vhost?
>
>
> Mit sonnigem Gruß
> Carsten Bleicker
>
> ----------------------
>
> Carsten Bleicker
> Wülfingstraße 1
> 42477 Radevormwald
>
> E-Mail: carsten at bleicker.de
> Web: www.bleicker.de
> Twitter: @carstenbleicker
> Jabber: cbleicker at jabber.ccc.de
> Telefon: +49 (0)171-2690845
>
> > Am 03.03.2015 um 13:54 schrieb Mira <mira at modifiziert.com>:
> >
> > Yes, of course! Many times. And again, and again..
> >
> > My DocumentRoot is set to ../Web and with "Development" context it works
> > fine.
> > Only with "Production" context I get this 404 error..
> >
> >
> >
> >
> >> Support <wm at psoft.at> hat am 3. März 2015 um 13:38 geschrieben:
> >>
> >>
> >> have you tried to restart apache?
> >>
> >> I did a test. If I set document root not to var/www/.../Web I get Error 404
> >> in
> >> flow.
> >>
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: flow-bounces at lists.typo3.org [mailto:flow-bounces at lists.typo3.org] Im
> >> Auftrag von Mira
> >> Gesendet: Dienstag, 03. März 2015 13:24
> >> An: 'TYPO3 Flow mailing list'
> >> Betreff: Re: [Flow] Get an 404 error after switching to
> >> "production"-context
> >>
> >> Hey!
> >>
> >> 1) I have tried this, but nothing changes. I also have cleared all caches..
> >>
> >> 2) Yes
> >>
> >> 3) No, in my virtualhost configuration I have the following line for this
> >> vhost:
> >> SetEnv FLOW_CONTEXT Production
> >> And in my .htaccess-file there is no SetEnv directive.
> >>
> >> Thanks,
> >> Mira
> >>
> >>
> >>> Support <wm at psoft.at> hat am 3. März 2015 um 13:17 geschrieben:
> >>>
> >>>
> >>> hi,
> >>>
> >>> I had similar problems. this did it for me:
> >>>
> >>> 1.) do ./flow flow:core:setfilepermissions root www-data www-data
> >>>
> >>> 2.) is document root in your apache-config pointing to "Web" folder ?
> >>> e.g DocumentRoot /var/www/flow-base-distribution/Web
> >>> and <Directory /var/www/flow-base-distribution/Web>
> >>>
> >>> 3.) is SetEnv FLOW_CONTEXT Production enabled in your .htaccess in "Web"
> >>> directory?
> >>>
> >>>
> >>> -----Ursprüngliche Nachricht-----
> >>> Von: flow-bounces at lists.typo3.org
> >>> [mailto:flow-bounces at lists.typo3.org] Im Auftrag von Mira
> >>> Gesendet: Dienstag, 03. März 2015 12:19
> >>> An: TYPO3 Flow mailing list
> >>> Betreff: Re: [Flow] Get an 404 error after switching to
> >>> "production"-context
> >>>
> >>> Yes, its the same:
> >>>
> >>>
> >>> root at host:/var/www/flow3/timbo# FLOW_CONTEXT=Development ./flow
> >>> routing:list Currently registered routes:
> >>> 1. index Startpage
> >>> root at host:/var/www/flow3/timbo# FLOW_CONTEXT=Production ./flow
> >>> routing:list Currently registered routes:
> >>> 1. index Startpage
> >>>
> >>>
> >>>
> >>>> Bastian Waidelich <bastian at typo3.org> hat am 3. März 2015 um 12:10
> >>>> geschrieben:
> >>>>
> >>>>
> >>>> On 03.03.15, at 12:02, Mira wrote:
> >>>>
> >>>> Hi again,
> >>>>
> >>>>> When I hit this command:
> >>>>> ./flow flow:core:migrate
> >>>>>
> >>>>> I get:
> >>>>
> >>>>> [...] Skipping My.Timbo, the working copy is dirty [...]
> >>>>
> >>>> Core migrations generate git commits, but only if your git working
> >>>> copy does not contain local changes that aren't committed yet.
> >>>> If you stash/commit those changes, the core migrations should run
> >>>> through.
> >>>>
> >>>> However, that probably won't solve the actual problem being that
> >>>> your routing seems to behave differently depending on the context.
> >>>> And that should never be the case.
> >>>>
> >>>> Did you already compare the output of
> >>>>
> >>>> FLOW_CONTEXT=Development ./flow routing:list
> >>>>
> >>>> and
> >>>>
> >>>> FLOW_CONTEXT=Production ./flow routing:list
> >>>>
> >>>> ?
> >>>>
> >>>>
> >>>> --
> >>>> Bastian Waidelich
> >>>> _______________________________________________
> >>>> Flow mailing list
> >>>> Flow at lists.typo3.org
> >>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> >>>>
> >>> _______________________________________________
> >>> Flow mailing list
> >>> Flow at lists.typo3.org
> >>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> >>>
> >>>
> >> _______________________________________________
> >> Flow mailing list
> >> Flow at lists.typo3.org
> >> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> >>
> >>
> > _______________________________________________
> > Flow mailing list
> > Flow at lists.typo3.org
> > http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>