[GH-ISSUE #37] Unable to install twofactor_sms in production environment #18

Closed
opened 2026-02-26 05:32:26 +03:00 by kerem · 4 comments
Owner

Originally created by @Dretech on GitHub (Apr 9, 2018).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/37

Hi Christoph,

In my test nextcloud environment towfactor_sms is running fine. I also wanted to use the two factor sms in my production environment. I followed the steps you gave me (for my test environment) and there are no errors. The logfile data/nextcloud.log does not give new entries. But after entering my password I get the screen below:
afbeelding

Translation: Unable to send message. Try again or contact your administrator.

Can you give me some hints how to solve this problem?

Kind regards,

André

Originally created by @Dretech on GitHub (Apr 9, 2018). Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/37 Hi Christoph, In my test nextcloud environment towfactor_sms is running fine. I also wanted to use the two factor sms in my production environment. I followed the steps you gave me (for my test environment) and there are no errors. The logfile data/nextcloud.log does not give new entries. But after entering my password I get the screen below: ![afbeelding](https://user-images.githubusercontent.com/10683755/38496586-6fc93d1a-3bfe-11e8-9aa2-54dee0de0541.png) Translation: Unable to send message. Try again or contact your administrator. Can you give me some hints how to solve this problem? Kind regards, André
kerem closed this issue 2026-02-26 05:32:26 +03:00
Author
Owner

@ChristophWurst commented on GitHub (Apr 9, 2018):

Phew, that is hard to tell. Do you have a debugger set up? Then you could set a break point at https://github.com/nextcloud/twofactor_sms/blob/master/lib/Service/SmsProvider/PlaySMS.php#L69, which is where errors should be caught.

<!-- gh-comment-id:379730085 --> @ChristophWurst commented on GitHub (Apr 9, 2018): Phew, that is hard to tell. Do you have a debugger set up? Then you could set a break point at https://github.com/nextcloud/twofactor_sms/blob/master/lib/Service/SmsProvider/PlaySMS.php#L69, which is where errors should be caught.
Author
Owner

@Dretech commented on GitHub (Apr 16, 2018):

Thanks for your reply. I enables debug in the nextcloud config.php. The last line of data/nextcloud.log is:

`{"reqId":"9A63ynYw4WCWZeLG88Vu","level":3,"time":"2018-04-09T10:38:43+00:00","remoteAddr":"","user":"--","app":"PHP","method":"--","url":"--","message":"include_once(): Failed opening '/usr/share/webapps/nextcloud/apps/twofactor_sms/appinfo/../vendor/autoload.php' for inclusion (include_path='/usr/share/webapps/nextcloud/3rdparty/pear/console_getopt:/usr/share/webapps/nextcloud/3rdparty/pear/pear_exception:/usr/share/webapps/nextcloud/3rdparty/pear/pear-core-minimal/src:/usr/share/webapps/nextcloud/3rdparty/pear/archive_tar:/usr/share/webapps/nextcloud/apps') at /usr/share/webapps/nextcloud/apps/twofactor_sms/appinfo/app.php#21","userAgent":"--","version":"13.0.1.1"}

Does that logline give a meaningful explonation why the 2fa is not running?

<!-- gh-comment-id:381572035 --> @Dretech commented on GitHub (Apr 16, 2018): Thanks for your reply. I enables debug in the nextcloud config.php. The last line of data/nextcloud.log is: `{"reqId":"9A63ynYw4WCWZeLG88Vu","level":3,"time":"2018-04-09T10:38:43+00:00","remoteAddr":"","user":"--","app":"PHP","method":"--","url":"--","message":"include_once(): Failed opening '\/usr\/share\/webapps\/nextcloud\/apps\/twofactor_sms\/appinfo\/..\/vendor\/autoload.php' for inclusion (include_path='\/usr\/share\/webapps\/nextcloud\/3rdparty\/pear\/console_getopt:\/usr\/share\/webapps\/nextcloud\/3rdparty\/pear\/pear_exception:\/usr\/share\/webapps\/nextcloud\/3rdparty\/pear\/pear-core-minimal\/src:\/usr\/share\/webapps\/nextcloud\/3rdparty\/pear\/archive_tar:\/usr\/share\/webapps\/nextcloud\/apps') at \/usr\/share\/webapps\/nextcloud\/apps\/twofactor_sms\/appinfo\/app.php#21","userAgent":"--","version":"13.0.1.1"} Does that logline give a meaningful explonation why the 2fa is not running?
Author
Owner

@ChristophWurst commented on GitHub (Apr 16, 2018):

include_once(): Failed opening '/usr/share/webapps/nextcloud/apps/twofactor_sms/appinfo/../vendor/autoload.php

Sounds like you did not run composer install in the app's directory and thus the vendor directory is missing.

<!-- gh-comment-id:381577853 --> @ChristophWurst commented on GitHub (Apr 16, 2018): > include_once(): Failed opening '/usr/share/webapps/nextcloud/apps/twofactor_sms/appinfo/../vendor/autoload.php Sounds like you did not run `composer install` in the app's directory and thus the `vendor` directory is missing.
Author
Owner

@ChristophWurst commented on GitHub (Aug 21, 2018):

Assuming this is resolved -> closing

<!-- gh-comment-id:414670164 --> @ChristophWurst commented on GitHub (Aug 21, 2018): Assuming this is resolved -> closing
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/twofactor_gateway-nextcloud#18
No description provided.